Ya, there are definitely some good ideas with RogueWave. Nothing that we couldn't implement though. ;-)
And thanks for helping me make my point. We'll see where the cookie crumbles soon I guess. Travis ---- Original Message ---- From: Jeff Schnitzer <[EMAIL PROTECTED]> Sent: 2002-04-24 To: Turbine Torque Users List <[EMAIL PROTECTED]> Subject: crossdb > From: Jeff Schnitzer > > I would like to eventually see Criteria replaced with something that > looks and works a lot like RogueWave's DBTools.h++: > > http://www.roguewave.fr/support/docs/dbtug/4-5.cfm#451 Wow, to respond to myself (now that I've read the Jakarta general list and looked at Crossdb), it looks like someone has already implemented such a creature. I think there is a lot to be learned from the RogueWave example, for instance their handling of joins is quite a bit more sophisticated. You never need to explicitly specify a join; a join automatically occurs when columns from two different tables are compared. For instance, look at these examples: http://www.roguewave.fr/support/docs/dbtug/5-2.cfm#522 (pardon the C++, of course) The nice thing about this approach is that joins are then completely encapsulated by the Where clause. This means that if, in my idyllic fantasy world, WhereClause replaced the Torque Criteria, joins could still be specified. Travis, there was an awful lot of resistance to Crossdb on the Jakarta general list because I don't think anyone understood that you're trying to provide an abstraction of SQL, not of higher-level concepts like JDBC or databases. Unless that point is clear, it's going to be as hard to "sell" in this community as a new MVC webapp framework <smirk> :-) Jeff Schnitzer [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
