> 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.
yep... ;-)
Record.getSaveString() does the same thing. If the Record being updated is
an INSERT, UPDATE or DELETE, getSaveString() is able to very quickly figure
out how the Record will be updated and return the appropriate string.
(a Record is a collection of Values. essentially it is a "Row" + "Column
Values" in the database)
> Looks pretty slick.
It is. This API kicks ass. Very little overhead and will save you literally
hours worth of programming if you are working a lot with a database (who
isn't? ;-) )
> Do you think it is pretty stable at this point?
It is /very/ stable...there have been a few showstopper bugs...mostly due to
my lack of hard core testing...but I have made a point to fix all of the
bugs within 24 hours so you won't be screwed if something doesn't work.
Plus, you have source code...so they are easily fixable by you. ;-)
anyways, please subscribe to either the town or village mailing list and
lets discuss this there. ;-)
thanks,
-jon
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]