Steve Crawford wrote:
> My vote is to add "Appendix I. Abbreviations". Don't know if it's
> practical for 8.3 documentation but it would be nice to add even if it
> only has a few entries as additional ones could be collected via the
> user notes.
>
> I suggest as a discussion starting-point the following inclusion criteria:
>
> 1. Any abbreviation/acronym that appears in the PostgreSQL documentation
> (even if those terms may not be PG specific - we shouldn't assume that
> everyone knows them). Good documentation practice recommends defining
> abbreviations the first time they are used. Better still, ensure that
> they are in the abbreviation list.
Isn't this just what the ABBR tag in html is for?
--
Alban Hertroys
[EMAIL PROTECTED]
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
---------------------------(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
