From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas Lockhart) |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org, zalman(at)netcom(dot)com |
Subject: | Re: [HACKERS] Re: [SQL] Column name's length |
Date: | 1999-06-02 08:51:50 |
Message-ID: | m10p6kY-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > How about something like this: if the code finds that the names are
> > too long when forming an implicit index name, it truncates the names
> > to fit, and you are OK as long as the truncated name is unique.
> > Comments? Objections? I think I could argue that this is a bug fix
> > and deserves to be slipped into 6.5 ;-)
>
> I understand some folks think this is a problem, but have been
> reluctant to include a "randomizer" in the created index name since it
> would make the index name less clearly predictable. May as well use
> something like "idx_<procid>_<timestamp>" or somesuch...
>
> No real objection though, other than aesthetics. And those only count
> for so much...
I've been wondering for some time why at all to build the
index and sequence names from those table/fieldnames. Only to
make them guessable?
What about building them from the tables OID plus the column
numbers. That way, auto created sequences could also be
automatically removed on a DROP TABLE because the system can
"guess" them.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-06-02 09:24:07 | Re: [HACKERS] Re: [SQL] Column name's length |
Previous Message | Hiroshi Inoue | 1999-06-02 08:48:22 | RE: [HACKERS] Open 6.5 items |