action_owl
20th March 2012, 06:08 PM
To ease installations of our in-house software I created some RPMS and a YUM repo, and they are working great for installing and upgrading the application. However, I haven't really wrapped my head around a method of properly handling databases and schema updates.
As of now, the app is installed with RPM, then a user loads a sql file.
mysql -u foo -p < fooapp.sql
If we update the app's schema, we have to manually update the app's database,
Before I go and building anything new into our app to handle schema updates I was wondering if there might be some RPM magic that I don't know about that would help me handle database updates. My guess is no, but I'm always open to new perspective or maybe some general best practices for this sort of thing.
Thanks!
As of now, the app is installed with RPM, then a user loads a sql file.
mysql -u foo -p < fooapp.sql
If we update the app's schema, we have to manually update the app's database,
Before I go and building anything new into our app to handle schema updates I was wondering if there might be some RPM magic that I don't know about that would help me handle database updates. My guess is no, but I'm always open to new perspective or maybe some general best practices for this sort of thing.
Thanks!
