Kodo jdoql oracle problem

Question

Hi there,
In my project, I have a jdoql query (select column1 from table1 where column2 == ''). It works fine with DB2 since DB2 supports empty string. When I moved it to oracle, the query doesn't get translated into something like (select column1 from table1 where column2 is null).
I am using openjpa.jdbc.sql.oracleDictionary in kodo property.
What are my options to handle this problem ?
kodo.log:
1024786 TRACE [WorkerThread#0[127.0.0.1:4318]] openjpa.jdbc.SQL - <t 981328, conn 5861567> executing prepstmnt 10850513
SELECT t0.TIMEFRAME
FROM VM0610 t0
WHERE t0.SITE = ?
[params=(String)  ]

Answer 1

Sasha-
I can't seem to reproduce this problem, either in the 2.5 or
upcoming 2.3.0 version. My test case is very simple: I have
an object that has a HashSet of Strings, I save the object with
10 entries, retrieve it (both with the same PM and a new one),
and the 10 entries still exist. Can you try this test case,
and see if it works? If it does, can you send us as much
of your code as possible, so we can try to reproduct it?
Also, any additional information you can enter into the
bug report would be useful:
https://bugzilla.solarmetric.com/show_bug.cgi?id=198
Sasha Haghani <[email protected]> wrote:
Does anyone know of a problem with HashSets in recent releases of Kodo? We
are currently working with 2.2.4 SP 1 and are running into the following
problem...
An existing persistence capable class (Group) had a number of simple fields
in it, as well as on HashSet, and a few HashMaps. The HashSet had Strings in
it, while the HashMaps are String to String, and String to complex objects.
All persistence of Group was occurring properly in the past. A recent
version of Kodo has introduced a problem where the HashSet contents
(Strings) are no longer persisted, but the simple fields and HashMap
contents are still being persisted ok. What is also interesting is that
there seems to be a relationship to the age of the Group object. Existing
Group objects seem to persist cleanly. New Group objects, which have been
made persistent and have been written out to the db (so should really be
identical to existing ones), exhibit the problem with the HashSets.
Can you shed any light on this? Thanks.
Sasha Haghani--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code