> >
> > > 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.
Another idea would be to truncate table and column names equally to fit
in NAMEDATALEN, then if that is not unique, start replacing the last
letters of the string with number until it is unique:
tabnamecolnametabnamecolnam1tabnamecolnam2tabnamecolna32
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
