Forum OpenACS Development: Re: Bug Stomp! (13th & 14th july)
I think the solution here is to remove those scripts and create new ones that follow the right order. For example in the case of acs-content-repository there would be a new script named: upgrade-5.2.0d18-5.2.0d19.sql wichi includes the sql scripts defined in upgrade-5.1.5-5.2.0a1.sql.
- Create upgrade scripts to change current constraints names
- Change creation scripts in order to have correct name constraints for fresh installations
- Fix funcion content_type__create_type for pg and content_type.create_type for oracle to create constraints of tables created automatically whit the estandar form
Anyway, our consensus is that you needn't bother with upgrade scripts. Let's just make the fresh installs pass the AA tests. Constraint naming errors don't really break anything, just make it harder to find which constraint died if you don't use unique names, and without a standard naming convention people tend to duplicate names.
So if you want to take on the last two items you've listed, that's sufficient.
And will be greatly appreciated!