View Issue Details

IDProjectCategoryView StatusLast Update
0000084Database Workbench v4Compare & Migrationpublic2014-03-19 11:54
ReporterFabio Peralta Assigned ToMartijn Tonies  
Status closedResolutionfixed 
PlatformWindowsOSWindows XPOS VersionSP3
Fixed in Version4.4.5 
Summary0000084: Stored procedure: the variables with default value had to be last parameters
DescriptionDuring database update, from the IDE, the last parameter of a stored procedure can be any data type.
I my previous db version, the last field of my sp was a Char(1) (Domain named D_YesNo) with default value = N.
During update, a new field (integer) was added in the end as last parameter and it was saved successfully.

Using comparing tool to generate a script, the domain was replaced by Char(1) type and during script execution, db error reporting that fields with default value had to be last ones.

Steps To Reproduce- Previously created sp had as last field a Domain D_YesNo (Char(1)) with default value = N.
- Added new field (any type, but in my case, an integer) on design
- commit changes (last field was integer and previous was domain)
- Compare database with previous
- Export script with difference
- Close comparing tool
- Run script on old db
  Dynamic SQL Error
  SQL error code = -204
  can not define a not null column with NULL as default value
  invalid clause --- 'defaults must be last'
TagsNo tags attached.
DBMS & Version


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2011-09-19 09:16 Fabio Peralta New Issue
2011-09-26 15:01 Martijn Tonies Status new => acknowledged
2014-03-05 09:42 Martijn Tonies Assigned To => Martijn Tonies
2014-03-05 09:42 Martijn Tonies Status acknowledged => assigned
2014-03-06 13:08 Martijn Tonies Status assigned => resolved
2014-03-06 13:08 Martijn Tonies Fixed in Version => 4.4.5
2014-03-06 13:08 Martijn Tonies Resolution open => fixed
2014-03-19 11:54 Martijn Tonies Status resolved => closed