Re: Locale-dependent case conversion in {identifier}
От | Nicolai Tufar |
---|---|
Тема | Re: Locale-dependent case conversion in {identifier} |
Дата | |
Msg-id | 003a01c298b6$0ae42970$8016a8c0@apb.com.tr обсуждение исходный текст |
Ответ на | 7.4 Wishlist ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
Ответы |
Hard-coded PUBLIC in pg_dump
|
Список | pgsql-hackers |
----- Original Message ----- From: "Hannu Krosing" <hannu@tm.ee> To: "Nicolai Tufar" <ntufar@apb.com.tr> Cc: <pgsql-hackers@postgresql.org> Sent: Saturday, November 30, 2002 5:41 PM Subject: Re: [HACKERS] Locale-dependent case conversion in {identifier} [ ... ] > > could it just be that we store identifiers in lower case, whereas most others > (including SQL spec IIRC)have them in upper case ? That seem to be the case. All the databases I used, automaticaly convert identifiers to upper case. And they all do it using ASCII-only conversion. > > Could you try the grant in both databases also in lower case ? > > i.e.: > > grant select on a to public; The statement works in both databases. But the problem is that it was pg_dumpall who created SQL statements with PUBLIC. Why pg_dumpall does not enclose identifiers in quotes, like: REVOKE ALL ON TABLE "tamara2" FROM "public"; insted of REVOKE ALL ON TABLE tamara2 FROM PUBLIC; as it does now. I will make an attempt to modify pg_dump accordingly, and will send a patch to the list. Regards, Nic
В списке pgsql-hackers по дате отправления: