Re: [DOCS] [HACKERS] timestamptz alias
Moving to -docs On Tue, Oct 03, 2006 at 12:13:46PM -0400, Andrew Dunstan wrote: > Tom Lane wrote: > >Markus Schaber <[EMAIL PROTECTED]> writes: > > > >>Here's a small patch that adds an appropriate explanation. > >> > > > >If we're going to document these aliases, what of float4, float8, and bool? > >Also, although the docs mention int2/int4/int8, it's more or less left > >to the reader's imagination to deduce what they are. > > > >Perhaps it'd be better to provide a small table of recognized type > >aliases, rather than inserting equivalent notes into three or four places. > > > > > > > you mean like the table here? > http://momjian.us/main/writings/pgsql/sgml/datatype.html An issue I've seen with the docs is that for chapters that have a lot of sections (such as 8), the section list at the start of each chapter fills the screen, so it's easy to miss the fact that there's more info beneath the list (which is wy presumably most folks never knew that table existed). I think the ideal way to handle this would be to put the table of contents in a side-bar and flow the text around it. But that could be a real bear to do in docbook/sgml, so perhaps it would be better to just force the TOC for each chapter onto it's own page (and ensure the overview/introduction text shows up in the TOC). -- Jim Nasby[EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] [HACKERS] timestamptz alias
Jim C. Nasby wrote: On Tue, Oct 03, 2006 at 12:13:46PM -0400, Andrew Dunstan wrote: Perhaps it'd be better to provide a small table of recognized type aliases, rather than inserting equivalent notes into three or four places. you mean like the table here? http://momjian.us/main/writings/pgsql/sgml/datatype.html An issue I've seen with the docs is that for chapters that have a lot of sections (such as 8), the section list at the start of each chapter fills the screen, so it's easy to miss the fact that there's more info beneath the list (which is wy presumably most folks never knew that table existed). I think the ideal way to handle this would be to put the table of contents in a side-bar and flow the text around it. But that could be a real bear to do in docbook/sgml, so perhaps it would be better to just force the TOC for each chapter onto it's own page (and ensure the overview/introduction text shows up in the TOC). I would like a frame driven version of the docs (c.f. doxygen, javadoc, etc.). The we would not need contents links at the top of each chapter like this. Navigating the HTML docs is less than pleasant. Unfortunately, I don't have enough time or docbook-fu to be able to do this. cheers andrew ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [DOCS] Texinfo docs/target
Patch applied. Thanks. --- Andreas Seltenreich wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > > Andreas Seltenreich wrote: > >> Now I'm wondering, if it'd be worth fixing the index and some minor > >> encoding deficiencies (e.g. medium-length dashes end up as > >> "[mdash]"), and adding Autoconf support in order to make it a proper > >> target. > > > > We probably won't ship it with the default distribution, but I don't see > > any harm in at least providing build support for it initially. > > The index seems to work with more recent versions of DB2X, and the > apparent encoding problems turned out to be an overlook in the > postgres.xml target. > > I had to run makeinfo with the --no-validate option, mostly because > the info design doesn't allow duplicate node names. However, it > doesn't seem to impair navigation besides addressing nodes by name, > and since most of the duplicate names are nodes like "Changes" in the > release notes section, I don't think it will be more of a nuisance > than being unable to look up Pi in the index... > > I figured adding autoconf support for db2x/info wouldn't be very wise > as long as the experimental postgres.xml target the new rules depend > on doesn't have any either. > > Patch attached. > > regards, > andreas > > > ---(end of broadcast)--- > TIP 4: Have you searched our list archives? > >http://archives.postgresql.org -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] bug in psql-ref
Patch applied. Thanks. --- Andreas Seltenreich wrote: > While testing the texinfo target, I noticed the following bug in the > psql reference. Declaring a printed character as part of the control > sequence is likely to confuse readline about what is on the screen, > causing unreliable line editing. > > Patch attached. > > regards, > andreas > > > ---(end of broadcast)--- > TIP 5: don't forget to increase your free space map settings -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] [HACKERS] timestamptz alias
Jim C. Nasby wrote: > I think the ideal way to handle this would be to put the table of > contents in a side-bar and flow the text around it. It's all CSS, so this should be doable. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
