Home
TeamSite
DataDeploy 5.2 can't insert null into DATETIME clm
clogan
I am using DataDeploy 5.2 and trying to deploy null into a DATETIME field in a SQL Server 2000 database. I want the user to be able to enter "09/01/2004" or nothing into a DCT and either have "09/01/2004" or null be inserted into the table. I can easily get a date into the database but I can't put null in there consistently.
Here are some options I know of:
1. Allow an empty field to be saved into the DCR and have 01/01/1900 be inserted into the database (a trigger can be written to update the record to null)
2. Write code in the tuple processor to check for "" and remove the field from the hashtable which does insert null into the database. What really happens is that the datadeployment ignores the field. The problem is that if you already have a date in that field, it won't be updated to null but stay the same.
3. Call SQL in the tuple processor to update the field to null before the deployment and then try option #2. A problem is that you can't roll this transaction back and you are left with null if the DataDeployment fails.
Anyone have any better ideas?
Will I have this same problem when I upgrade to Teamsite 6.2?
-Craig
Find more posts tagged with
Comments
clogan
Hopefully no one will care about this note because everyone has gotten off of the now unsupported DataDeploy 5.2.x.
After practically forcing support by gun point to look at the problem of not being able to insert null into a DATETIME field, they found it is a bug.
I was actually on DataDeploy 5.2.0 sp1. They had me upgrade to 5.2.1, and that broke even more things.
In DataDeploy 5.2.1 sp1, we found that nested foreign key groups don't work.
By nested foreign key groups, I mean: You have 3 tables(groups) A, B, and C. A is the root group and B has a foreign key to A. C has a foreign key to B.
This extra bug of nested foreign key groups was also deemed a bug.
I am still crossing my fingers as I am upgrading to OpenDeploy/DataDeploy 6.0 to see if the two problems above work.
-Craig
Internet Engineer
Reader's Digest
www.rd.com
www.changeone.com
clogan
I have been able to test both bugs with OD/DD 6.0 and they aren't bugs with this version.