On Fri, Jan 29, 2010 at 1:57 AM, Rickard Öberg <[email protected]> wrote:
> So we're still back at what to do for RDBMS? Hand-coding or something like > iBatis seems like the best option. What others are there? I agree with the Hibernate observation in general. If this is indeed a central piece of the overall strategy to drive adoption, I think we should not do a less than optimal approach, the least dependencies of others, and just do it right with our own set of tools. The number of RDBMSes we need to support are small, and I doubt we need any of the advanced extensions that typically drives RDBMS inter-operability. The main remaining issue is "types", which can be a hairy chapter (there are so many of them in each, and they are not same even if they have the same name). But, personally I think it can be managed fairly easy. First step is still to figure out what kind of support we would provide. Hibernate, for instance, would support all kinds of mapping from multiple tables, merging result fields to member variables, sub-querying and what not. Should we go for an "anti-corruption layer" approach where the 'mapping' is 1-to-1 between any existing tables to newly written composite states, which then with composite mechanism are exposed to the domain model? Probably need a Requirements Statement, preferably in Jira around this whole topic or it can quickly get out of hand, me thinks. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
