Re: Runtime Config Option for identifier case preservation
| От | Michael W Mitton |
|---|---|
| Тема | Re: Runtime Config Option for identifier case preservation |
| Дата | |
| Msg-id | 200501141510.31166.mmitton@ssi-c.com обсуждение исходный текст |
| Ответ на | Runtime Config Option for identifier case preservation (Michael W Mitton <mmitton@ssi-c.com>) |
| Список | pgsql-patches |
Opps! I have my logic backwards below. Those two SQL sets should be set parser-ignore-case = true; select "Address_id" from "Address"; set parser-ignore-case = false; select Address_id from Address; On Friday 14 January 2005 02:51 pm, Michael W Mitton wrote: > Attached is a patch to allow the user to change the behavior of postgres > with reguards to case sensitivity on unquoted identifiers. This does not > change the default behavior of converting unquoted identifiers to > lowercase, but does allow (for instance, and I'm absolutly -not- pulling > from personal experience here <g>) a large project to run under postgres > that did run under MySQL a whole bunch easier. > > for example, these two SQL statements sets are identical > set parser-ignore-case = false; > select "Address_id" from "Address"; > > set parser-ignore-case = true; > select Address_id from Address;
В списке pgsql-patches по дате отправления: