Also, I really don't understand how a project can allow a developer to commit changes to code where the database fields have changed without any responsibility to update the ddl scripts as appropriate. Are others supposed to guess what the new fields are? It seems really unprofessional not to tie the two actions together.
Hank On Sat, Dec 17, 2011 at 10:12 AM, Greg Logan <[email protected]> wrote: > On 12/17/2011 11:28 AM, Christopher Brooks wrote: > > Hey hank, > > > > The autogeneration of ddl does not work reliably. The mysql scripts are > the most up to date, and there was a resolution on list to reduce our > coverage just to one script (the mysql one) to help eliminate these issues, > so the postgres scripts should be removed from future releases. Instead, > we'll advertise in our release docs any community contributed scripts for > non mysql dbs. > > > > So, I'd try with mysql right now, and autogen off (there were > significant db naming convention changes in this last rc). > >
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
