Good reference, Steve.
So, given a CachedRowSet, it's easy to snag a data set and puruse it at
your leisure, since the database connection is automatically closed by
the RowSet. I've been using them for retrievals extensively, and they
are an absolute pleasure to use.
CachedRowSets are also mutable so you can update, deleted, and insert
rows rows remotely, and (if your DBMS supports transactions) send the
changes back to whence they came.
Now, the next step is to create a RowSet from scratch to insert a new
record to a new table. Given this, there doesn't seem to be any reason
to have a seperate value object bean for a data set that is coming from
or going to a persistent store.
I'm going to take a whack at this tonite, so anyone who'd done this and
has any pointers, please let me know!
> Steve Salkin wrote:
>
> Take a look at sun's CachedRowSet now available in early release.
>
> http://www.javaworld.com/javaworld/jw-02-2001/jw-0202-cachedrow.html
>
> S-
>
