Data Deploy Null Fields Issue

Hi,

I am using Data deploy to deploy a DCR content to the database. This DCR has some non mandatory fields and hence these fields can be null.

In my data deploy configuration file I have set the attribute for these fields as allows-null="yes" and while creating the database table I have made these columns as NULLABLE but this does not seem to be working.

If while saving the DCR i do not enter anything in these fields and exceute data deploy even though it does not throw any error but does not save anything also in the tables.

When i just put a space in these fields it gets deployed successfully but when i query the table now for null fields it returns me the fields where I have entered the space as NULL only.

Here is the sample from the data deploy configuration file

< column name="promo_text" data-type="VARCHAR(254)" value-from-field="product_container/0/product/0/promo_text/0" allows-null="yes" is-url="no"/ >

Has anyone faced the same issue with data deploy and null fields, if yes please help me here.

Find more posts tagged with

Comments

Adam Stoller

What database are you using?
I've seen cases where some databases (like MySQL if I remember correctly) didn't work with null fields but did with empty ("" or space) fields - and, again if I recall correctly, it was a case of how the empty field was treated as part of the query that caused the issue.

dolly1

Hi,

Thanks for the reply. I am using oracle 10g.

Jcse

Hi,

Thanks for the reply. I am using oracle 10g.

Oracle 10g works with empty fields also as well as NULL field also.So,if you are entering space it takes it as empty field,that's why the query bring the result.

Faizi

Hi,

Thanks for the reply. I am using oracle 10g.

Are you using Livesite deployment?
If yes then check livesite-opendeploy.jar file is available at //od-home/userlib folder. If not then copy this jar from //iw-home/install/opendeploy/userlib folder.

RonaldV

Oracle 10g works with empty fields also as well as NULL field also.So,if you are entering space it takes it as empty field,that's why the query bring the result.

Yes, this looks like a Oracle-feature and NOT a datadeploy problem: Oracle, at least in previous versions, tends to remove leading/trailing whitespace from a varchar(2)-column and then, if the result is an empty string, store that result as null. That is just the way Oracle works.

You might have some luck if you either:
- change the column type to 'char' but this will have more impact then you might expect!
- maybe change some database-configuration-setting
- ask an oracle expert

Cheers, Ronald