Weekly report for 11 July 2010 on Project "Database Module + FuzzySQL"
This week I have:
Added the usage of database drivers when creating connections using connection string, provided by user. Except for TDS driver. But this feature is not implemented completely yet, because only PostgreSQL and SQLite drivers can create a connection by given connection string. All other drivers require database parameters: database name, user name and password. So there's no big use of DbConnect() version using connection string, because except for PostgreSQL and SQLite the connection string will just be parsed and connection parameters extracted, which could be the same way given in a Scilab struct. There must be a way to set some provider-specific database connection parameters, provided in a connection string, but for this I will need to dig into drivers documentation.
Added CheckLhs and CheckRhs calls to all functions to check number of input and output parameters
- Provided demos for all functions. Demos are using 2 local databases: a Access databse 'Dbt.mdb', for which a QODBC provider is used and SQLite database 'addressbook', for which QSQLITE provider is used
- Provided help for the rest of functions
Implemented functions DbFirst(), which sets a record pointer in a resultHandler to a first record, and DbLastInsertId(), which returns the Id of last inserted record
Next week
Prepare the module for release. Write some unit tests ( better late than never ). Check all helps and demos. Look for way to set provider-specific parameters for establishing a connection when a connection string is provided for DbConnect(), but at least database name, user and password will be parsed from it to esatablish a connection. The connection string usages for DbConnect() must also be tested for all providers.