Making KDb work with databases creates elsewhere without importing them
Introduction: KDb depends on kexi__* objects even when accessing native database features. Historically this was caused by limitations of SQLite and having simple support for multiple databases. The problem is however that there are existing databases and users expect to be able to use them with Kexi, and possible extend them with Kexi-specific features.
The Goal: Making KDb work without importing
- add to Connection: virtual bool drv_tableNames(QStringList& tablenames) = 0; (from KexiMigrate)
- this iterates through the database schema
- add to Connection: virtual bool drv_readTableSchema(QString& tableName, KexiDB::TableSchema& tableSchema) = 0; (from KexiMigrate)
- this reads the native table schema and creates TableSchema object
- add to Connection: virtual bool drv_viewNames(QStringList& tablenames) = 0;
- map it to SELECT queries in Kexi
Fix Krazy warnings
Fix Krazy checker's warnings. Especially:
- add d-pointers - [dpointer] warning
- move inline code from headers to .cpp - [inline] warning
- fix typos
For other types of warnings ask the maintainer first - there are false positives!
Add unit tests
This page was last modified on 23 August 2015, at 13:09. Content is available under Creative Commons License SA 4.0
unless otherwise noted.