A new topic, 'Best Practices regarding Stored Procedures.', has been made on a
board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=82.new#new
The text of the topic is shown below:
Hello LB Community!
I am once again working on the LB integration with a multi-module Maven2
project and am hoping to get some feedback on some best practices in regards to
managing Stored Procedures with LB on SQLServer... That being said, here's
some background: We currently have 50+ SPs in our system that get modified from
time to time and I'm wondering what the best way to approach versioning these
would be. Since we are implementing LB on a legacy DB and will not have the
need to install a full db, we have decided it would be best to use ALTER
statements in all of our SP sql files. I have toyed with the idea of using a
databaseChangeLog that contains changeSets with the runOnChange attribute set
to true that includes a sqlFile element pointing to each of our SP sql files.
This way, when a dev makes a change to the SP, they needn't worry about
creating a new changeset for the modification. LB will pick up on the fact
that it has been changed and will run the changeset. A dev would create a new
changeSet element when a new SP is created. I guess the biggest question I
have in regards to going this route is how to handle rollbacks? I'm aware of
the rollback element but would hate to require that a dev populate this element
with the version of the SP sql file that existed before modification (IMO, this
would be too awkward for devs to keep up with)... What do others do to solve
this seemingly common problem?
Any and all feedback is greatly appreciated in advance.
Thanks!
-Ryan
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The LiquiBase Community Forum Team.------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
