No cursor when compared with ADO

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After a dataset has been populated, it no longer reflects changes in
database. It is the shortcoming I found in ADO.NET. In ADO, we have dynamic
recordset, keyset recordset which can reflect the changes to database done by
other users immediately. Why can't I find these useful stuff in ADO.NET?
 
It would appear that you have not done any reading abour ADO.NET. If you had
you would know that ADO.NET and ADODB are completely different animals and
cannot be compared to one another.

If you wish to do so, you are quite free to use ADODB and, if you do, you
will have all your 'legacy' functionality.

I do recommend, however, that you take the time to study ADO.NET more deeply
and I think that you will find that is is far more flexible than you seem to
think at he moment.
 
Samuel1234 said:
After a dataset has been populated, it no longer reflects changes in
database. It is the shortcoming I found in ADO.NET. In ADO, we have dynamic
recordset, keyset recordset which can reflect the changes to database done by
other users immediately. Why can't I find these useful stuff in ADO.NET?
Click to expand...

Because an open server side cursor is very bad for scalability. Say you
have a database server and a desktop application installed on 1000
desktops targeting that database server. Without serverside cursors,
that's easy. With server side cursors, the database server CAN have at a
given moment 1000 open resultsets. That's not that great for the
database server.

It's also unnecessary. After all, the data you're viewing on the screen
is a snapshot of the data at time T. It's stale the second you fetch it.

FB

--
 
Back
Top