Changelog automatic infrastructure

[GoogleCodeExporter]

We're facing a problem with the existing functionality of DbDeploy, which
is today's need for creating the CHANGELOG table manually

This could be solved by DbDeploy creating the CHANGELOG table if none exists.

In order for this to work, we chose to wrap the DbDeploy code (3.0M2)
rather than patching it, but you get the idea ;-)

Would be great if this functionality would be part of your baseline in the
future!

Original issue reported on code.google.com by peter.p....@gmail.com on 4 Feb 2010 at 12:43

Attachments:

• changelog_auto.zip

[GoogleCodeExporter]

Thanks peter.  Dbdeploy has avoided this in the past for two reasons:

1. the awkwardness of ensuring the correct database-specific changelog table 
script is executed
2. a safety net so that dbdeploy never accidently can run against a database 
you don't want it to

The first is no doubt fixable, and the second I guess we could add a parameter 
(default false) to enable this 
functionality.

The attached zip file appears empty (perhaps because it's taken me so long to 
look at it) - could you reupload?

Original comment by gtack...@googlemail.com on 10 May 2010 at 8:24

• Added labels: Priority-Medium, Type-Enhancement
• Removed labels: ****

[GoogleCodeExporter]

I agree with Peter here.  It would be wonderful to have this done 
automatically.  Our group has embraced DB Deploy and each time we show it to 
another group in our company, we need to start them off with a block off Java 
code that creates the table if it doesn't exist.

Perhaps even instead of creating it via DB Deploy, you could let us create it 
as, for example, a 000_create_changelog_table.sql which would be run if the 
changelog table isn't found.  That's just a thought.  Then developers could 
write the SQL but DB Deploy would automatically execute it for us.

Original comment by superwes...@gmail.com on 20 Sep 2013 at 5:04

• Added labels: ****
• Removed labels: ****