RedGateDatabaseOptionsTransactionIsolationLevel bugged

Automated deployment for web applications and databases

RedGateDatabaseOptionsTransactionIsolationLevel bugged

Postby matthoneycutt » Mon Apr 07, 2014 4:52 pm

There's a bug in Deployment Manager 2.4.6.8. The RedGateDatabaseOptionsTransactionIsolationLevel seems to have a check for valid transaction isolation levels, but the problem is that check has misspelled "committed." When I enter "READ COMMITTED" as the value for this property, I get this error when the agent attempts to deploy everything:

2014-04-07 10:42:13 -05:00 ERROR READ COMMITTED is not a valid transaction isolation level. It must be one of: READ UNCOMITTED, READ COMITTED, REPEATABLE READ, SNAPSHOT, SERIALIZABLE
2014-04-07 10:42:13 -05:00 ERROR Caused by:
2014-04-07 10:42:13 -05:00 ERROR -READ COMMITTED
2014-04-07 10:42:13 -05:00 ERROR Parameter name: value

Notice the incorrect spelling of 'COMMITTED' in the list of valid values.
Just for fun, I tried passing in the incorrectly-spelled 'READ COMITTED,' but that blew up (as it should) with a syntax error from SQL.

Any suggestions on how to work around this problem?
matthoneycutt
 
Posts: 7
Joined: Mon Apr 07, 2014 4:48 pm

Postby DavidSimner » Tue Apr 08, 2014 10:58 am

Sorry! I've just fixed this (internal reference 6501fb34361b), and we're currently expecting to ship it tomorrow on our regular Release Wednesday.
DavidSimner
 
Posts: 54
Joined: Thu Feb 04, 2010 6:05 pm

Postby matthoneycutt » Thu Apr 10, 2014 12:44 pm

Thanks, seems to be working fine now!
matthoneycutt
 
Posts: 7
Joined: Mon Apr 07, 2014 4:48 pm


Return to Deployment Manager

Who is online

Users browsing this forum: No registered users and 0 guests