| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | PostgreSQL development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bringing PostgreSQL torwards the standard regarding |
| Date: | 2004-04-25 20:21:52 |
| Message-ID: | 408C1DE0.8060907@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manfred Koizar | 2004-04-25 20:26:56 | Number of pages in a random sample (was: query slows down with more accurate stats) |
| Previous Message | Andrew Dunstan | 2004-04-25 18:16:19 | Re: Bringing PostgreSQL torwards the standard regarding |