On Friday, June 15, 2007, 3:40:39 PM, vinays84 <[EMAIL PROTECTED]> wrote:
> I apologize if I'm asking questions that are answered in the dev guide, I'm > just trying to gain a quick understanding. > So, if I have an object defined for a specific table, then I want to include > a query which involves another table, I'd have to expand my original object > to incorporate the additional columns, taking away its table specific > status? Yes, in short. As Brandon says, you're mapping the *result* of a query, so if you use a different result, then you (probably) need a different object. Using a Map might let you side-step that, although you're trading one thing for another there. > How would one handle queries not known at time of development (for instance > for ad-hoc reporting)? > Does the SQL Maps framework go hand in hand with the DAO framework? i.e. > Should I be learning the DAO framework to properly use SQL Maps. Well, you need something, but not specifically the DAO framework - In fact, I'd suggest looking at the Spring DAO rather than the Ibatis DAO. Another thing that you might want to take a look at, once you've got a basic setup working, is the Abator utility. That examines a DB table and produces various of the files needed to use iBATIS on it, but might be a bit unclear if you've not got the context that creating a basic 'by-hand' setup will have given you. /Gwyn
