Michael, Regarding changing the code in half an hour, it may be possible for your use but we have to assess the possible impact on existing users and maybe provide a property settings to switch to the old behaviour.
As to my request to "submit a full list of changes that are required for JDO, including public interfaces and internal modifications. We can move from there." This includes the necessary JDBC interface methods in addition to internal changes. Your report is encouraging but it doesn't mean that someone else's application may not rely on another non-conforming aspect that we don't know of. Different JDO wrappers may also have quirks in their use of JDBC. We shouldn't attempt to support well defined standards without someone doing a methodical review first. Your input is most welcome. If there is someone who could help provide the patch for Michael to continue his tests, please do. Fred Toussi --------------------------------- Michael Vorburger wrote: <snip> To make Hsqldb usable as datastore in most common JDO implementations, without much extra work, at this point in time may not actually require much work on the hsqldb side!!! The above "Including null rows in select" is a blocker however. We are hoping to use this as part of an (inhouse) framework and have over 10'000 lines of JUnit test code, of which most already pass with using Hsqldb instead Oracle as a datastore; and other than the above have not identified any other major problem to date. ------------------------------------------------- This shouldn't be too difficult to change. Classes such as Expression and Select are responsible for building the results. We will only get involved if the purpose is a proper implementation of JDO. If you want to help, as a first step please . Fred Toussi PS: Please note the list address: [EMAIL PROTECTED] -----Original Message----- Michael Vorburger wrote: Any chance you could point me in the right direction where in the source code we could "patch" this ourselves? PS: As quick background, we are evaluting the use of hsqldb as embedded datastore for a JDO-based application. According to the JDO specification, comparison with null attributes should exclude elements from a result set. Of course you could argue "that's not our problem", and strictly technically speaking I of course agree, however if there is a way around this, it would be great, and I believe could give hsqldb more visibility in the JDO community. I am willing to put in some time to help here... ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
