On 12/17/2011 4:26 PM, Hank Magnuski wrote: > 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.
This is definitely an issue, however we have not had processes in place to manage or test these changes before now. In the future we hope to eliminate this manual update process using the changes fro MH-8335. G > Hank > > On Sat, Dec 17, 2011 at 10:12 AM, Greg Logan <[email protected] > <mailto:[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 _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
