Re: [gnome-db] Minor API change and MySQL [update/delete]_row



> right. That is, we remove all the const's in the API, except for things
> like gda_value_get_string and so on.

Since I have gda-data-model.[ch], gda-row.[ch] hanging around
uncommited, I'll implement this and send in a patch.  So here're what
we've decided,

  1) remove const from GdaRow* and GdaValue* in both function
     arguments and return types.

  2) There's only one _model_get_row().  The user should check with
     _is_updatable() to see the model can be updated.

Here're what's left to be decided,

  3) The conditions for insertable and editable sql model are
     different.

       insertable:  have all non-null columns that have no default values

       updatable:   have at least one non-null unique key

     Should we replace _is_editable() with _is_updatable() and
     _is_insertable()?

  4) Are these staying or going away?

	(gda_data_model_begin_edit):
	(gda_data_model_end_edit):
	(gda_data_model_cancel_edit):
	(gda_data_model_is_editing):

  5) Do we want a separate header for functions that only providers[1]
     use?  -- we can still commit while this is being decided.

:-),


[1] or whatever Rodrigo call a peice of code (end user's or our) that
    manage underlying data.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]