On 6/21/07, Piotr Pokora <[EMAIL PROTECTED]> wrote: > "Vivien Malerba" <[EMAIL PROTECTED]> wrote: > > > As for the API extension, it could be possible to add some parameters > > to the execute() function implemented within each provider to specify > > what GType is expected for each column of the SELECT query being > > executed (note that the current operating mode would still be > > useable). > > I think I do not follow. > Do you mean I can invoke gda_connection_execute_select_command with > GdaParameterList ?
Yes, you can pass a GdaParameterList object to the gda_connection_execute_select_command() function, see the documentation about it for what named parameters it can contain. > > If yes, does it mean I can use gda_parameter_list_add_param_from_value? > If yes, does, 'name' argument is column name? No, the parameters is the GdaParameterList object help specify some aspects of the returned data model (such as if you want a random access data model, or a cursor based one). > > And if I can use GdaParameterList, what's the correct way to use it? See the docs. > > GdaParameterList* gda_parameter_list_new (GSList *params); > requires params, while gda_parameter_list_add_param_from_value will > return GdaParameter but still requires GdaParameterList. You can use gda_parameter_list_new (NULL) and then call gda_parameter_list_add_param () each time you want to add a parameter, or you can use gda_parameter_list_new_inline(). In both cases, you can pas NULL for the dict argument. Vivien _______________________________________________ gnome-db-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-db-list
