there is a blank to null string field conversion available. Use that. This was
originally written (by me) to make Oracle and SQL server compatible. Oracle treats
blank strings as nulls. You could use this to satisfy your requirement here.
m
-----Original Message-----
From: Marcelo Magno [mailto:[EMAIL PROTECTED]
Sent: Sun 6/22/2003 11:07 AM
To: OJB Users List
Cc:
Subject: Empty String
I am having problems saving empty strings on the Sql Server with OJB.
I have some string fields that couldn't be null or empty strings. On
Access we had a option to mark where we want to permit empty strings or not, in Sql
Server I was not able to find anything compared to this.
The problem is, even if I do not send the empty string to my Object,
telling that this field should be null, OBJ saves an empty string.
I am working with Exception Trowing to the interface, and as the empty
string is saved on Sql Server, so I do not receive any exception (as Ojb have saved
the empty string) on the interface.
Is there a way to manage OBJ try to save, or not to save (allowing the
null on the column) this empty string on the table?
Thanks in advance,
Marcelo Magno
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
