Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Hi Drew,

Not really...Also, normally one would allow the tool to generate unique
index names - for example creating a FK relation will automatically
create required indexes, adding a PK to a table also.

I'm a little surprised.  Although I've got over twenty years of database 
development experience, it is largely in FoxPro (a dBase improvement), 
although with a little of a few others. I've not seen, and certainly 
wouldn't want, an insistence on automatically named indices.

And sorry if this is off track - but I just want to be sure that you are
referring to index names and not column names

Yes, I'm definitely talking about index names.
I took up Andreas' idea of importing my dbase-type files into an HSQL LO 
database.  It didn't realise the tables already had primary key fields.  I 
usually call these iId (as integer ID fields), and so want an index 
(called iId) on each table. I can't do that in HSQL.

I know there's an idea that index names should include table names, which 
would completely eradicate the issue, it's just that I don't agree :-)

It's a (perhaps) interesting discussion point rather than a problem 

Thanks for the info
Mark Stanton
One small step for mankind...

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.