Centralizing features for GdaConnection
I would like to present a brief idea for a possible way of using Libgda.
1 - The connection class is an object only for connection and connection information to the database. For example, SSL, TLS connections, among other ways. It is also possible through this class to obtain connection information. 2 - Create classes for DML commands. 3 - Create classes for DDL commands
For example methods like: gda_connection_delete_row_from_table
We would have something like: gda_dml_delete_row
This is just an idea, a decentralization of gda connection, transferring functionality to other classes specific to a particular operation.