Re: [gnome-db] Minor API change and MySQL [update/delete]_row
- From: Paisa Seeluangsawat <paisa unt edu>
- To: Rodrigo Moya <rodrigo gnome-db org>
- Cc: GDA <gnome-db-list gnome org>, Laurent Sansonetti <laurent datarescue be>
- Subject: Re: [gnome-db] Minor API change and MySQL [update/delete]_row
- Date: Sat, 15 Nov 2003 19:23:54 -0600
In non-transactional provider, what do you mean by "batch updating"?
What does it do when _cancel_edit() or _end_edit()? We agreed that
the query get sent by _update_row(). Isn't that the end of it?
What more are there to do?
> > 2) What is supposed to happen to (local and server) data when a user
> > opens models A and B in the same connection, edit A and B, then
> > _model_cancel_edit(A), _model_end_edit(B)?
> >
> depends on the provider I guess. For postgres, we might use nested
> transactions, for others, whatever it needs, etc.
Even with nested transaction, I still have no idea how to implement
it.
Anyway, I'm getting my hand off this record updating issue. After
several e-mails, I still have no idea what a user should expect from
these functions. I'll just work on other parts of libgda/gnomedb.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]