Clever Geek Handbook

About JDBC RowSet

I know what a RowSet is and that's it; what I would like to know is if it works correctly and is already accepted, or if it still has its bugs and is not as widely accepted as the classic ResultSet. it looks good to me so far, but I want to hear more experienced opinions on the matter.

+2


source to share


2 answers


I think there are two factors in deciding if a RowSet is right for you:

1) Can you get the whole result in memory? Sometimes you need to parse the result set one line at a time and don't just get everything in memory right away.



2) Have you tested your JDBC driver for RowSet behavior?

I think # 2 is where you start your question. The truth is that it is mostly implementation dependent if the given RowSet is reliable and production-ready. In theory, you could use a RowSet implementation from a vendor other than the JDBC driver, and that should work too.

+3


source


RowSet

  • RowSet makes life easier for all JDBC programmers. No more Connection Objects, Operator Objects, just one RowSet will do it all for you.
  • Rulers make it easy to send tabular data over the network. They can also provide scrolling result sets or updatable result sets when the underlying JDBC driver does not support them.
  • The RowSet object follows the JavaBeans model for notification properties and events; it is a JavaBeans component that you can combine with other components in your application.
  • Strings can have many different implementations to fill in different needs. These implementations fall into two broad categories, rows that are related and those that are disabled.


RowSet Tutorial

+3


source






More articles:


All Articles