KDb/TODOs: Difference between revisions

From KDE Community Wiki
< KDb
No edit summary
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Making Predicate work with databases creates elsewhere without importing them==
==Making KDb work with databases creates elsewhere without importing them==
Introduction: KexiDB 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.
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 Predicate work without importing
The Goal: Making KDb work without importing


Ideas:
Ideas:
Line 18: Line 18:


==Junior Jobs==
==Junior Jobs==
Fix [http://ebn.kde.org/krazy/reports/playground/libs/predicate/index.html Krazy checker's warnings]. Especially:
===Fix Krazy warnings===
Fix [http://ebn.kde.org/krazy/reports/playground/libs/kdb/index.html Krazy checker's warnings]. Especially:
*add d-pointers - [dpointer] warning
*add d-pointers - [dpointer] warning
*move inline code from headers to .cpp - [inline] warning
*move inline code from headers to .cpp - [inline] warning
*fix typos
*fix typos
For other types of warnings ask the maintainer first - there are false positives!
For other types of warnings ask the maintainer first - there are false positives!
===Add unit tests===
See [[../Tests/]].


==Marketing==
==Marketing==
Ideas:
Ideas:
*Predicate is already Qt Only. After first release list it on http://inqlude.org
*KDb is already Qt Only. After first release list it on http://inqlude.org
*Prepare small pleasant 'visit card' web site e.g. at http://predicate.kde.org
*Prepare small pleasant 'visit card' web site e.g. at http://kdb.kde.org
*Logo?
*Logo?

Revision as of 13:09, 23 August 2015

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

Ideas:

  • 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

Optional:

  • add to Connection: virtual bool drv_viewNames(QStringList& tablenames) = 0;
    • map it to SELECT queries in Kexi

SQLite Driver

Junior Jobs

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

See Tests.

Marketing

Ideas: