×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi James,
I've used them, or tried to. The real purpose I wanted it for was
built-in optimistic concurrency, but I had to make workarounds for almost
every operation because the implementation was so bad. Actually, I should
have jumped on the open source JDK 7 and made it right, but... (insert
excuses here.) That was 2005, but I don't see where any substantial (or
maybe any) have been made.
As to "is it still needed?" I think it depends on your usage. If you
are really looking to cache *data*, eight ball says odds are good there are
better ways. If you really need to access the data as a rowset, but
disconnected, or have scrollability etc when the driver/database doesn't
provide it, and those kinds of reasons, then I'd say they definitely have a
place. But there really should be better implementations in the standard
API.
IMO, etc.
Joe Sam
Joe Sam Shirah -
http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum:
http://www.ibm.com/developerworks/java/
Just the JDBC FAQs:
http://www.jguru.com/faq/JDBC
Going International?
http://www.jguru.com/faq/I18N
Que Java400?
http://www.jguru.com/faq/Java400
----- Original Message -----
From: "James Perkins" <jrperkinsjr@xxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Friday, November 07, 2008 11:50 AM
Subject: Anyone using CachedRowSet
Hello All,
I'm just curious to see if anybody is using the JSR-000114 JDBC(TM) Rowset
Implementations?
I have used this in the past, but is it still needed? Are there better
way's
to cache results?
Thanks in advance,
James R. Perkins
--
midrange.com
