Forum OpenACS Development: Upgrade script naming convention

In the tutorial Writing upgrade scripts, Jade Rubick suggests:
Create a file in sql/postgres/upgrade called packagename-1.0b1-1.0b2.sql
But in a concrete package, reality looks different. E.g., (ls -R, omitting CVS directories):
bug-tracker/sql/oracle:
bug-tracker-create-packages.sql  CVS
bug-tracker-create.sql           upgrade
bug-tracker-create-tables.sql    upgrade-1.2d10-1.2d11.sql
bug-tracker-drop-data.sql        upgrade-1.2d2-1.2d6.sql
bug-tracker-drop.sql

bug-tracker/sql/oracle/upgrade:
CVS                      upgrade-1.2d9-1.2d10.sql  upgrade-1.3d1-1.3d2.sql
upgrade-1.2d8-1.2d9.sql  upgrade-1.3a7-1.3a8.sql
Some upgrade scripts are in the upgrade directory, some are above. None use the package name, rather all start with "upgrade-". (For my taste, both prefixes are too redundant.)

My question: What's the current convention? How should new upgrade scripts be named today?

Collapse
Posted by Dave Bauer on
Bugtracker is wrong, and unfortunately Jade's advice is mistaken.

Upgrade scripts go under sql/database/upgrade and are named
upgrade-oldversion-newversion.sql

Collapse
Posted by Christian Brechbuehler on
Thank you!

I conclude that some are right, e.g., bug-tracker/sql/oracle/upgrade/upgrade-1.3a7-1.3a8.sql

Collapse
Posted by Jade Rubick on
Christian:

Good catch. Please update my tutorial in the documentation if you have the time!

Jade