Re: PGDN content information proposal - Mailing list pgsql-www
| From | Oleg Bartunov |
|---|---|
| Subject | Re: PGDN content information proposal |
| Date | |
| Msg-id | Pine.GSO.4.63.0506301532190.19218@ra.sai.msu.su Whole thread Raw |
| In response to | Re: PGDN content information proposal ("Gevik Babakhani" <gevik@xs4all.nl>) |
| Responses |
Re: PGDN content information proposal
("Gevik Babakhani" <gevik@xs4all.nl>)
|
| List | pgsql-www |
On Thu, 30 Jun 2005, Gevik Babakhani wrote: > I agree, the pub_id is generated automatically like HT1234(.htm) meaning the > public name would be HT (for a HowTo document and 1234 as internal id) I don't like this artificial binding and name flooding. > > Regards, > Gevik. > > >> -----Original Message----- >> From: pgsql-www-owner@postgresql.org [mailto:pgsql-www- >> owner@postgresql.org] On Behalf Of Oleg Bartunov >> Sent: Thursday, June 30, 2005 1:03 PM >> To: Gevik Babakhani >> Cc: pgsql-www@postgresql.org >> Subject: Re: [pgsql-www] PGDN content information proposal >> >> On Thu, 30 Jun 2005, Gevik Babakhani wrote: >> >>> Dear All, >>> >>> >>> >>> I would like to start a discussion regarding the content information and >>> structure we would like to have in PGDN. >>> >>> Here is the proposal: >>> >>> >>> >>> The content in PGDN has the following: >>> >>> 1. Content id (of course) (sequence generated number) >> >> we need two id's once we allow updating document. One is a pub_id - >> publicly accessed persistent id and msg_id - internal id. >> >>> >>> 2. Author (user or author id) >>> >>> >>> >>> 3. major version (numeric like 3) >>> >>> 4. minor version (numeric like 2 >>> >>> 5. revision. (numeric like 5) >>> >>> This makes a document version of 3.2.5 >>> >>> >>> >>> 6. content applies to a PostgreSQL version. (varchar) (like "all pg >>> versions", "8.x","7.x" >>> >>> 7. title (varchar) >>> >>> 8. A short description (varchar) (this would be the content >> introduction) >>> >>> 9. status (varchar) (E for editing for published, R for rejected) >>> >>> 10. the actual content or the story >>> >>> 11. date created >>> >>> 12. date updated >>> >>> 13. content type (like how-to, article, tutorial, etc ..) >>> >>> >>> >>> Do we need more information about a PGDN content? Please let me know >> what >>> you think. >>> >>> >>> >>> Ps. the category and the keywords of the content are saved elsewhere. >>> >>> >>> >>> Regards, >>> >>> Gevik. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> Regards, >> Oleg >> _____________________________________________________________ >> Oleg Bartunov, sci.researcher, hostmaster of AstroNet, >> Sternberg Astronomical Institute, Moscow University (Russia) >> Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ >> phone: +007(095)939-16-83, +007(095)939-23-83 >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 5: Have you checked our extensive FAQ? >> >> http://www.postgresql.org/docs/faq > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83