01, 2010 4:29 PM
To: Apache Torque Users List
Subject: Re: Revisited: Oracle and the empty string
Thomas Vandahl t...@apache.org wrote:
On 01.10.10 21:47, Thomas Fischer wrote:
In my experience, it is no problem if you keep that fact in mind. It
just
makes the code non-portable
just a question about a best-practice. We are trying to implement an
XML-to-DB-mapper service on Oracle. The (existing) XSD defines some
fields which distinguish between not set (null) and empty (). How
do others handle this in Oracle? Especially within Torque?
In my experience, it is no
On 01.10.10 21:47, Thomas Fischer wrote:
In my experience, it is no problem if you keep that fact in mind. It just
makes the code non-portable to another database (you only query for not
null and know it's also not empty in oracle, but not dor other databases).
Is it a problem for yaou if and
Thomas Vandahl t...@apache.org wrote:
On 01.10.10 21:47, Thomas Fischer wrote:
In my experience, it is no problem if you keep that fact in mind. It
just
makes the code non-portable to another database (you only query for not
null and know it's also not empty in oracle, but not dor other
