Someone has requested this once before. I think my answer was something like: "if you want to implement it, go ahead"....
I think it is a little bit of scope creep but we do already define some indexes so i'm relaxed about that. My view is that you can't expect SchemaExport to replace a DBA who knows how to properly performance tune a database for a production system. Not sure quite what the best approach would be. Perhaps an index-name attribute of <column> element. That way multiple columns could be mapped to the same index.... ----- Original Message ----- From: "Yaron Zakai" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, September 28, 2002 12:19 AM Subject: [Hibernate] Defining column index for properties > Hi, > > In a use case where the database schema is almost fully controlled by the > mapping file, does it makes sense to add the functionality of defining an > index on a single property? The next level would of course be defining an > composite index, using several properties/columns. > > Is this in the scope of Hibernate? > > Thanks, Yaron. > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
