On 3/1/07, Armin Burgmeier <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Armin Burgmeier wrote: > > There still seems to be another problem with GdaDataModelHash (the > > grid does not update its UI after committing), but this has probably > > nothing to do with update_row. > > I filed another bug for this, > http://bugzilla.gnome.org/show_bug.cgi?id=413258. > > What I actually try to do is showing a GdaDataModel retrieved by > gda_connection_execute_select_command (from a sqlite provider). I am not > sure how common this is, but it is pretty easy to achieve and therefore > used as introduction in the libgnomedbmm tutorial documentation. > > The patch I attached to the bug report fixes the mentioned problems, but > I am not sure whether it does it the right way. Perhaps I just got some > code semantics wrong. In either case, I would be glad to hear how (and > whether) showing and/or modifying a GdaDataModelHash is supposed to work. >
Thanks for the patch. However I doubt it will be very usefull: the data returned from a SELECT command can now be edited (in most if not all the cases since the provider's own implementations of the returned data model inherits GdaDataModelHash) but it won't actually write back the modifications to the database for the simple reason that in most cases it won't know what to write, so the modified data cannot be used (except in some are cases). What I believe is better is to create a GdaDataModelQuery data model for which you'll give a SELECT query, and optionnally INSERT, UPDATE or DELETE queries so it knows how to actually write the data you modify back to the database. Regards, Vivien _______________________________________________ gnome-db-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-db-list
