diff -NurB libgda-1.0.3-orig/doc/C/libgda-docs.sgml libgda-1.0.3/doc/C/libgda-docs.sgml --- libgda-1.0.3-orig/doc/C/libgda-docs.sgml 2004-04-01 04:22:09.000000000 -0500 +++ libgda-1.0.3/doc/C/libgda-docs.sgml 2004-04-01 06:04:12.000000000 -0500 @@ -2,7 +2,7 @@ libgda"> GNOME-DB"> -Igalia, S.L.'> +Igalia, S.L.'> API"> DBMS"> DSN"> @@ -28,7 +28,6 @@ "> - @@ -391,23 +390,23 @@ will need to install a few packages in the following way: - $ apt-get install package-names + $ apt-get install package-names These are the packages you will need for this: - libgda2-1 - libgda2-common - libgda2-dev - libgda2-doc - libgda2-dbg + libgda2-1 + libgda2-common + libgda2-dev + libgda2-doc + libgda2-dbg You can obtain information about any packages with: - $ apt-cache show package-names + $ apt-cache show package-names If you cannot find this packages, you must include in @@ -637,8 +636,8 @@ providers specific information. - There was a little bugIt can be fixed, but it - is better not to run the risk of it., and it + There was a little bugIt can be fixed, but it + is better not to run the risk of it., and it is that gda_config_save_data_source() does not create the configuration directory The command type we most commonly use is GDA_COMMAND_TYPE_SQL because we will only - focus on &SQL; queriesThere are other command types, as &XML; and so on. + focus on &SQL; queriesThere are other command types, as &XML; and so on. @@ -1244,13 +1243,13 @@ LINKEND="data-model">data models). You have two ways to do this: - + - gda_data_model_execute_single_command() + gda_data_model_execute_single_command() - + - gda_data_model_execute_command() + gda_data_model_execute_command() @@ -1340,29 +1339,29 @@ Let's see the functions we need: - - gda_data_model_get_n_rows() + + gda_data_model_get_n_rows() - - gda_data_model_get_n_columns() + + gda_data_model_get_n_columns() - - gda_data_model_describe_column() + + gda_data_model_describe_column() - - gda_data_model_get_column_title() + + gda_data_model_get_column_title() - - gda_data_model_get_column_position() + + gda_data_model_get_column_position() - - gda_data_model_get_row() + + gda_data_model_get_row() - - gda_data_model_get_value_at() + + gda_data_model_get_value_at() - - gda_row_get_value() + + gda_row_get_value() @@ -1514,7 +1513,7 @@ - + Managing values Values returned by functions of managing data are - - gda_value_free() + + gda_value_free() - - gda_value_is_null() + + gda_value_is_null() - - gda_value_copy() + + gda_value_copy() - - gda_value_compare() + + gda_value_compare() - - gda_value_stringify() + + gda_value_stringify() @@ -1637,20 +1636,20 @@ classes, and they are: - - gda_transaction_new () + + gda_transaction_new () - - gda_connection_begin_transaction () + + gda_connection_begin_transaction () - - gda_connection_commit_transaction () + + gda_connection_commit_transaction () - - gda_connection_rollback_transaction () + + gda_connection_rollback_transaction () - - gda_command_set_transaction () + + gda_command_set_transaction () @@ -1809,17 +1808,17 @@ Here you see the functions to manage errors: - - gda_error_get_description() + + gda_error_get_description() - - gda_error_get_number() + + gda_error_get_number() - - gda_error_get_source() + + gda_error_get_source() - - gda_error_get_sqlstate() + + gda_error_get_sqlstate() @@ -1920,9 +1919,9 @@ There is no problem about calling several times to this function because if you save an existing data source, it - is replaced, so it could be advisableBut you must think + is replaced, so it could be advisableBut you must think of security if you distribute the source code because people would see - the passwords of your databases. to save the data source + the passwords of your databases. to save the data source each time you want to create the connection. @@ -1971,9 +1970,9 @@ A normal query is a query that return data. This is made as a data model, analogous to GdaRecordset in the old - versionNow you have a Now you have a GdaRecordset class, - but it is not recommended.. + but it is not recommended.. As you can see in the following example, the function we use to @@ -1987,11 +1986,11 @@ As in the case of non queries, you + LINKEND="gda-connection-execute-non-query">non queries, you must not use several semicolon-separated sentences, because you - have a special function to do thisgda_connection_execute_command - (), but it is not recommended. + (), but it is not recommended. @@ -2037,6 +2036,7 @@ changes using &SQL;, so we consider data models not to be modifiable. + Accessing directly to columns @@ -2080,7 +2080,6 @@ The following sections describe the API available for &GDA; applications. &libgda-init; - &libgda-batch; &libgda-blob; &libgda-client; &libgda-command; @@ -2268,7 +2267,7 @@ Tables GDA_CONNECTION_SCHEMA_TABLES "name" (name of table, optional) - name, owner, comments, SQL definition + name, owner, comments, SQL definition Tables' parents @@ -2355,7 +2354,7 @@ describe_column Returns information about a given column, in the form of - a GdaFieldAttributes. + a GdaFieldAttributes. @@ -2363,10 +2362,10 @@ Retrieves a row from the data model. This function is very important for the implementation of editable data models. What this function - returns is a GdaRow, which providers - should uniquely identify (via gda_row_set_id). + returns is a GdaRow, which providers + should uniquely identify (via gda_row_set_id). This is needed so that later on, client applications can use the same - GdaRow returned by this method in + GdaRow returned by this method in the update_row and remove_row methods. @@ -2387,9 +2386,9 @@ Before a data model can be edited, client applications must call the - gda_data_model_begin_edit + gda_data_model_begin_edit function, which emits the "begin_edit" signal on the - GdaDataModel class. So, providers + GdaDataModel class. So, providers should connect to this signal to be informed when the data model starts being editing. In the callback connected to that signal, it should start a transaction, for instance. @@ -2430,7 +2429,10 @@ - &libgda-server-provider; + + Details + &libgda-server-provider; +