Set the value for the node at the path formed using path_format and the ... ellipse (the rules are the same as
for glib.global.strdupPrintf).
Note that trying to set a value for a path which is not used by the current
provider, such as "/TABLE_OPTIONS_P/TABLE_ENGINE" for a PostgreSQL connection (this option is only supported for MySQL),
will <emphasis>not</emphasis> generate
any error; this allows one to give values to a superset of the parameters and thus use the same code for several providers.
Here are the possible formats of path_format:
<itemizedlist>
<listitem><para>If the path corresponds to a #GdaHolder, then the parameter is set to <![CDATA["value"]]></para></listitem>
<listitem><para>If the path corresponds to a sequence item like for example "/SEQUENCE_NAME/5/NAME" for
the "NAME" value of the 6th item of the "SEQUENCE_NAME" sequence then:
<itemizedlist>
<listitem><para>if the sequence already has 6 or more items, then the value is just set to the corresponding
value in the 6th item of the sequence</para></listitem>
<listitem><para>if the sequence has less then 6 items, then items are added up to the 6th one before setting
the value to the corresponding in the 6th item of the sequence</para></listitem>
</itemizedlist>
</para></listitem>
<listitem><para>If the path corresponds to a #GdaDataModel, like for example "/ARRAY/@COLUMN/5" for the value at the
6th row of the "COLUMN" column of the "ARRAY" data model, then:
<itemizedlist>
<listitem><para>if the data model already contains 6 or more rows, then the value is just set</para></listitem>
<listitem><para>if the data model has less than 6 rows, then rows are added up to the 6th one before setting
the value</para></listitem>
</itemizedlist>
</para></listitem>
</itemizedlist>
Set the value for the node at the path formed using path_format and the ... ellipse (the rules are the same as for glib.global.strdupPrintf).
Note that trying to set a value for a path which is not used by the current provider, such as "/TABLE_OPTIONS_P/TABLE_ENGINE" for a PostgreSQL connection (this option is only supported for MySQL), will <emphasis>not</emphasis> generate any error; this allows one to give values to a superset of the parameters and thus use the same code for several providers.
Here are the possible formats of path_format: <itemizedlist> <listitem><para>If the path corresponds to a #GdaHolder, then the parameter is set to <![CDATA["value"]]></para></listitem> <listitem><para>If the path corresponds to a sequence item like for example "/SEQUENCE_NAME/5/NAME" for the "NAME" value of the 6th item of the "SEQUENCE_NAME" sequence then: <itemizedlist> <listitem><para>if the sequence already has 6 or more items, then the value is just set to the corresponding value in the 6th item of the sequence</para></listitem> <listitem><para>if the sequence has less then 6 items, then items are added up to the 6th one before setting the value to the corresponding in the 6th item of the sequence</para></listitem> </itemizedlist> </para></listitem> <listitem><para>If the path corresponds to a #GdaDataModel, like for example "/ARRAY/@COLUMN/5" for the value at the 6th row of the "COLUMN" column of the "ARRAY" data model, then: <itemizedlist> <listitem><para>if the data model already contains 6 or more rows, then the value is just set</para></listitem> <listitem><para>if the data model has less than 6 rows, then rows are added up to the 6th one before setting the value</para></listitem> </itemizedlist> </para></listitem> </itemizedlist>