The modeler currently doesn't allow you to specify arbitrary indexes. This could be added to the wish list, but would mainly be used while developing a schema (not while maintaining an in-production schema).
My preferred approach is to have upgrade scripts that are checked into the SCM repository. You can use filenames like schema_001.sql, schema_002.sql, etc. Makes it easy to sequence them and is highly reproducible. It also clearly documents your changes. It would be a very difficult problem for the modeler to be able to automatically determine the required changes from one schema to another -- and you'd have to force the DBAs to run the modeler then, too. I don't know of a good schema migration tool. /dev/mrg -----Original Message----- From: Eric Lazarus [mailto:[EMAIL PROTECTED] Sent: Friday, May 19, 2006 7:15 AM To: cayenne user Subject: Can I use the CayenneModeler to set up indexes? If so, how? Can I use the CayenneModeler to set up indexes? If so, how? Can someone share an example, a screen shot or something? If not, how do others deal with this? Do I write a little shell script that does SQL queries to add those indexes when I re-gen the database? On a separate note, does anyone know a good schema migration tool we can use when we, after we deploy, we end up with changes to our relational and object models and we need to move data forward (and, in an emergency perhaps, backward)? Eric __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
