Re: [DOCS] Suggestion for Encodings table
Preston Landers wrote: > > http://www.postgresql.org/docs/8.0/interactive/multibyte.html#CHARSET-TABLE > > I would humbly suggest a few improvements to that Encodings table to > improve the clarity. > > Many of the entries clearly indicate the language or writing system, such > as WIN1256 = "Windows CP1256 (Arabic)" > > I would suggest that every single entry should be described that way with > the common language or writing system name. Even Unicode could say "All > languages". > > In particular, the "WIN" encoding just says "CP1251" -- this is Cyrillic > (Russian) but some people might just see the WIN and assume it's the > character set that Western/US Windows uses (CP 1252). > > It's an easy mistake to make and one I see repeated frequently on other > web pages (calling Windows "Western" CP 1251.) Someone reading English > language docs and seeing a "WIN" character set might naturally assume that > it is the English Windows character set. (Which BTW is not currently > supported by PG for conversions.) > > Some more examples that might improve clarity: > > LATIN5 should say "Turkish" > > LATIN6 should say "Nordic" > > ALT and KOI8 should say "Cyrillic" (or Russian) Great. Would you submit a patch to the SGML sources? -- Bruce Momjian| http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[DOCS] question regarding Example 2-4
Hi. I was reading the postgres tutorial and I was confused by this example. I'll post here the example and the given tables. Example 2-1. The Suppliers and Parts Database SUPPLIER SNO | SNAME | CITY SELLS SNO | PNO -+-+ -+- 1 | Smith | London 1 | 1 2 | Jones | Paris 1 | 2 3 | Adams | Vienna 2 | 4 4 | Blake | Rome3 | 1 3 | 3 4 | 2 PART PNO | PNAME | PRICE 4 | 3 -+-+-4 | 4 1 | Screw | 10 2 | Nut|8 3 | Bolt | 15 4 | Cam| 25 SELECT PNAME, PRICE FROM PART WHERE PNAME = 'Bolt' AND (PRICE = 0 OR PRICE < 15); will lead to the result: PNAME | PRICE + Bolt | 15 From what I understand, the select statement should query the PART table for records with PNAME equal to Bolt and having a PRICE of either 0 or less tahn 15. The row with PNAME Bolt has a PRICE EQUALto 15 so the select statement should have resulted to an empty set. Was my understanding wrong? Thanks,yen Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term'
[DOCS] Minor corrections in xfunc.sgml
Hello, This patch corrects typos in xfunc.sgml: 1646c1646 < /* b reference, fixed length */ --- > /* by reference, fixed length */ 1943c1943 < list of shared objects to be build from source file with same --- > list of shared objects to be built from source file with same Regards, Hashem Masoud __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [DOCS] Minor corrections in xfunc.sgml
Hashem Masoud wrote: This patch corrects typos in xfunc.sgml [...] Thanks; typos fixed in HEAD and REL8_0_STABLE. -Neil ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
