Wow. Good work Jon. I have been using some home-grown
stuff not nearly as slick. Once comment that I have that I have
enjoyed in my stuff when debugging is the ability to return
the sql that a method will create. For example, if you are
about to invoke set.save() in a servlet, do a:
System.err.println(set.sqlSave());
Which returns the sql that the save is going to be generated.
As I said, this is a great debugging tool because you can watch
what is going to happen.
Looks pretty slick. Do you think it is pretty stable at this point?
><http://www.working-dogs.com/town/>
>
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
