13 Dec 2001 13:22:19 +0100
On Thu, 2001-12-13 at 09:11, Adam Chester wrote:
> RE DataSet's:
> "That is, I can't imagine why somebody will get a picture of an
> entire database, modify it for a day, for instance, and then put it back
> to the database"
> Actually, this is kind of core the whole ADO.NET model (the disconnected
> DataSet's). The theory is you get the data as quickly as possible and then
> you are disconnected from the database server to avoid using (and locking)
> server resources.
yes, and it is a nice idea worth supporting it in gnome-db. I'm only
worried about the data loss that (I guess) users will encounter.
> Then once you complete your modifications (which are stored in the DataSet
> as being modified) it compiles a list of changes and calls the respective
> Update/Insert/Delete commands using the DBDataAdapter.
> It's not necessarily a "nightmare" as you put it, because you can easily
> implement concurency techniques to avoid modifying any data that was changed
> after you aquired your DataSet snapshot.
yes, that's why I said it might be a nightmare, because users will be
losing their modifications too often (in a multi-user, ever-changing
database). As you say, it can be really easy to just discard
modifications for rows/fields that have already been changed by someone
else, but this won't help too much that user.
Rodrigo Moya <email@example.com> - <firstname.lastname@example.org>
http://www.gnome-db.org/ - http://www.ximian.com/