search

evasong10 / dbdeploy

Automatically exported from code.google.com/p/dbdeploy
0 stars 0 forks source link

CLI consolidated output change_number wrong #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When using the -o flag from the CLI, the consolidated output file is formatting 
the change_number with a comma thousand separator, which then breaks the 
insert, as the column counts aren't correct. As you can see below the 
change_number should be 219001  not 219,001.

INSERT INTO changelog (change_number, complete_dt, applied_by, description)
 VALUES (219,001, CURRENT_TIMESTAMP, USER(), '219001_add_notify_to_user.sql');

Original issue reported on code.google.com by visseraj on 18 Nov 2010 at 7:42

GoogleCodeExporter commented 9 years ago 
Isn't this the same as issue 48 ?

Original comment by dwilkie2@gmail.com on 19 Nov 2010 at 8:16

GoogleCodeExporter commented 9 years ago 
Yes it is. My apologies, I searched for consolidated and didn't find a ticket 
with that in it.

Original comment by visseraj on 19 Nov 2010 at 1:56

GoogleCodeExporter commented 9 years ago 
And also the same as issue 36... which was fixed in r135.

Apologies for such a dumb error :(

I'll be looking to create a new binary release in the next few days hopefully 
as this is such a critical bug.

Original comment by gtack...@googlemail.com on 23 Feb 2011 at 5:40