I've come across recent updates in term of record sets being up-to-date to ensure that we are able to scroll backwards and forwards with the data it indicates.

My real question is why these were initially created for a forward only traversal. Can there be any impact while using latest version?

"latest versionInch is all about five years old.

forward only : it's the simplest method to implement. It's simplest to implement a Queue(FIFO) as opposed to a deque or linked list. Because the JDBC driver needs to browse the record in the DB, celebrate them Readily available towards the ResultSet readers FIRST COME FIRST SERVE.

Afterwards, they recognized that some desktop programs plus some wealthy internet based applications may want to scroll forwards and backwards without needing to keep intermediate representations, they made the decision to implement it.

Then came the updatable ResultSets where one can update the posts/rows of the ResultSet.

It is a very long time since I have checked out some of these things, however i think that initially the information was streamed, as well as for most of the JDBC motorists the Recordset was associated with low-level cursor procedures within the database.

The only real impact by using may possibly be on memory usage - however in almost all business cases you are not likely to notice and that i wouldn't be worried about it. When confronted with large datasets you will need to check out the way you fetch your computer data however i mean large within the "enterprise" feeling of the term - millions, otherwise vast amounts of records.

Packing a lot of features to the first version of JDBC might have slowed down lower the adoption of JDBC, because the suppliers might have taken longer to implement it.

Scrollable result sets is really a relatively rarely used feature in JDBC, therefore it wasn't essential to be there from the first day. Exactly the same is applicable towards the other fancy features in JDBC 2 and three.