Hi guys,
due to an upcoming idea on the Torque dev-list I / we thought about
adding a new SourceProvider to Torque.
That could, for example, possibly use JPA or JAXB annotations. In
times of webservices a lot of POJO classes with both kinds of
annotations are already existing and both sets of
Hi folks,
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?
Bye, Thomas.
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
