On Mon, Oct 13, 2008 at 12:39 PM, Michael Hunger <[EMAIL PROTECTED]> wrote:
> By now it uses a naming convention approach for mapping entities and > properties to database columns. OK, although isn't that troublesome, since AFAIK some RDBMSes are case-sensitive, or will that be hidden in the iBatis stuff? > If you remember correctly I suggested a direct JDBC or JEQUEL (my Java SQL > DSL which I also presented at the geek > cruise) entity store rather than the cumbersome ibatis handling a while ago. I am not toally negative to direct SQL, or something else, but I have fairly bad experiences with nuances between systems creating a lot of problems. I do realize that for the EntityStore it is probably only limited to 'type' differences and possibly String encoding. > I'll also think about the best way of integrating qi4j with an rdbms (most > probably existing legacy). We should discuss > that on the list and then use whatever library is suited best for our needs. > (Pure JDBC is still an option). Yes, I just want to make sure that we have a solution that is workable. iBatis might still be the best way... > For querying for example I could imagine rendering our query api queries to > SQL. The (hopefully) just form expression > trees that can be easily rendered (Alin?). Yes, that is another part where we could use RDBMS, and probably should implement due to "question marks" around RDF that people might have... > For just storing stuff into the entity store we just have to map the Entities > and ValueComposites conveniently onto > RDBMS tables and columns. So our problem is more a mapping problem for > storage and retrieval than a typesafe java > api for RDBMs access. Yes, for non-legacy stuff, some people will probably still want to use RDBMSes, and instead of arguing our head off, we could have EntityStore for it. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
