From: | ncm(at)zembu(dot)com (Nathan Myers) |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Truncation of object names |
Date: | 2001-04-13 20:59:29 |
Message-ID: | 20010413135929.Q3797@store.zembu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 13, 2001 at 04:27:15PM -0400, Tom Lane wrote:
> ncm(at)zembu(dot)com (Nathan Myers) writes:
> > We are thinking about working around the name length limitation
> > (encountered in migrating from other dbs) by allowing "foo.bar.baz"
> > name syntax, as a sort of rudimentary namespace mechanism.
>
> Have you thought about simply increasing NAMEDATALEN in your
> installation? If you really are generating names that aren't unique
> in 31 characters, that seems like the way to go ...
We discussed that, and will probably do it (too).
One problem is that, having translated "foo.bar.baz" to "foo_bar_baz",
you have a problem when you encounter "foo.bar_baz" in subsequent code.
I.e., a separate delimiter character helps, even when name length isn't
an issue. Also, accepting the names as they appear in the source code
already means the number of changes needed is much smaller, even when
you don't have true schema support.
Nathan Myers
ncm(at)zembu(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Burton | 2001-04-13 21:08:46 | Re: Truncation of object names |
Previous Message | Tom Lane | 2001-04-13 20:55:24 | Re: Truncation of object names |