On Sat, Nov 22, 2008 at 7:11 AM, Zsolt Koppany <[EMAIL PROTECTED]> wrote:
> My impression is that the ibatis community is much more programmatic than
> the derby one, I feel to much policy there (ibm, sun etc.), however (it is
> also important to understand) derby gets better and better and I don't
Larry,
I completely agree! I see NO value. NULL is NULL regardless whether or
not Integer, String or whatever.
We have seen several times that classes got by Sun deprecated and they
came back.
Of course it is an option waiting for couple of years and hoping that
the standard will be change
Here's my opinion on this, for what it's worth.
Neither derby nor ibatis are at fault here - both are doing what is
expected: Working within the constraints of a standard API from Sun
(JDBC).
The real issue here is that the standard API is kind of stupid in this case.
The crappy part of that is
Hi,
I figured out the issue. It was a combination of setting the
SetAutoCommitAllowed, DefaultCommitAllowed properties correctly. Also I had
assumed that DaoManagerBuilder.buildDaoManager will return the same instance
of Daomanager always ( like a singleton ). So I was creating the dao in my
Hi,
I attached the answer from the derby list.
I just wonder how effective the communication is between the derby and
ibatis communities.
Would it be really so complicated to fix the problem? Discussions about
standards are very important however the acceptance of API-s is more
important, a
