On Sat, 2002-11-30 at 07:57, Nicolai Tufar wrote: > With this, no matter what kind of "I" you used in names, > it is always going to end up a valid ASCII character. > > Would it be acceptable if I submit a path that applies this > special logic in src/backend/parser/scan.l if the locale is "tr_TR"? > > Because for many folks setting locale to Turkish would > render their database unusable. For, god forbid, if your > sql has a column name written in capitlas including "I". > It is not working. So I deeply believe that PostgreSQL community > have to provide a workaround for this problem. > > So what should I do?
In SQL in general and in postgreSQL in particular, you can always use quoted names and thus escape the stupidities of case conversion: grant SELECT ON "a" to "public"; should work everywhere (except Oracle and other DB's where it should be grant SELECT ON "A" to "PUBLIC"; ) I can't help you on Win32/VMS filenames ;) --------------- Hannu ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
