Re: Bringing PostgreSQL torwards the standard regarding
От | Andrew Dunstan |
---|---|
Тема | Re: Bringing PostgreSQL torwards the standard regarding |
Дата | |
Msg-id | 408C1DE0.8060907@dunslane.net обсуждение исходный текст |
Ответ на | Re: Bringing PostgreSQL torwards the standard regarding (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Bringing PostgreSQL torwards the standard regarding
|
Список | pgsql-hackers |
I wrote: > > > Alvaro Herrera wrote: > >> On Sun, Apr 25, 2004 at 12:23:55PM -0400, Andrew Dunstan wrote: >> >> >> >>> I don't think we should rush at this. All of these solutions are >>> based on the existing structures. I have started thinking about a >>> solution that would involve keeping two versions of catalog names: a >>> canonical name and a "name as supplied at creation". >>> >> >> >> Why do you want two names? Just keep the original casing, and a boolean >> saying if it's quoted or not. >> >> > > Because I was not just considering the upper/lower issue - refer to > the thread that relates to unquoted names with case preserved. Sorry - brain malfunction - yes, original casing plus boolean would work. In effect you could derive the canonical form from those two. cheers andrew
В списке pgsql-hackers по дате отправления: