rob wrote:
I work alongside Elias here at IBM and did a fair amount of the IBatis
work on Roller
Craig L Russell wrote:
Hi Elias,
Showing my ignorance of iBatis here, but I thought that iBatis was a
very thin wrapper around SQL.
It is
So if you support multiple databases, don't you need different SQL for
each one?
Not really, we now have support for DB2, Oracle and MySql and while we
did have to make some IBatis tweaks to get things working on Oracle we
have yet to find a case where we need to fire different SQL at different
back ends.
Hmmm, this part sounds questionable to me. As I said before, I don't
have any experience with iBatis so I don't know the full story, but if
iBatis can't guarantee database independence like many of the other ORM
solutions then that seems like a mess we wouldn't want to get into.
You say you have tested against DB2, Oracle, and MySql, but how many
versions? What about all the other dbs out there that have been used by
Roller thus far ... Derby, Hsql, Postgres, MSSql, others?
I think we *really*, *really* don't want to get into a situation where
users may have problems running Roller against the db of their choice
due to disparities in sql syntax. So that should be considered an
important criteria when choosing which solution to choose for the backend.
-- Allen
Is this an extended iBatis you are using or has iBatis changed in ways
that I didn't know about?
Regular Ibatis, no changes.
Rob
p.s. we will make a point of discussing features on this list going
forward, but it wasn't clear early in the project's life whether IBM
would permit us to submit code back to the community. There's still a
few final legal hurdles to clear internally, but it looks like we are
now in the final stages. Once complete there are probably 3 of us that
will need to do the code grant paperwork.
