I think I could get it cleanly added to Cayenne 3.1. I would probably have to upgrade the DBMerger, LoaderDeligate, DBLoader, DBEntity, create a MergerToken, and possibly upgrade DBAdapter. Someone else would have to upgrade the modeler since I am not up to speed with that code. I then would be able to contribute the changes back into the trunk code. So should I just checkout the trunk code, make the changes and then submit the diffs?
Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West River Road, Grand Island, New York, 14072, USA Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 * [email protected] * www.insysware.com CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you. -----Original Message----- From: George Stan [mailto:[email protected]] Sent: Sunday, January 17, 2010 5:06 AM To: [email protected] Subject: Re: Index modeling > > Are there any plans to add DB index definitions and > generation in the > > DBEntities in the near future? We are currently > managing these outside > > of the Cayenne xml and using SQLTemplates to generate > them when I sync > > the models to the DB. It would be nice if we don't > have to maintain that > > code if Cayenne would handle it for us. > > You could certainly put forward a patch for this work and > it would be welcomed. Should be simple enough to implement > the changes to the model schema and the modeler. > > There is already a Jira task open for this but I don't > believe anyone has started work. It is this JIRA issue: https://issues.apache.org/jira/browse/CAY-204 And it's one of the most (wanted and) voted feature request: https://issues.apache.org/jira/browse/CAY?report=com.atlassian.jira.plug in.system.project:popularissues-panel George.
