kexi project
Rapid Database Application Development
"Microsoft Access for Linux"

Home Download FAQ Support Features Handbook Screenshots Screencasts Compile Kexi Development Authors Contact License Sponsorship Translate This Site

wiki navigation:

Front Page
[info] [diff] [login]
[recent changes]
[most popular]
You can donate
to Kexi Project:
Via PayPal

Spread the word about Kexi!
Get Kexi Now!

Built on the KDE technology

Member of the Calligra Suite

No Software Patents!

KexiDataMigrationAndSharing / GeneralHints

1. Establish connection using Connection object and use its methods, like:

 Cursor* executeQuery( const QString& statement, uint cursor_options = 0)
 Cursor* prepareQuery( const QString& statement, uint cursor_options = 0)
 bool querySingleRecord(const QString& sql, KexiDB::RowData &data)

2. Why is there redundancy in the Migration framework compared to KexiDB, e.g. why there is KexiMigrate::drv_tablenames() if we have KexiDB::Connection::tableNames()?

Note that there is one important difference: For example KexiDB::Connection::tableNames() uses KexiDB::Connection::objectNames() which in turn, uses SQL. It is not a rule that the source of the migration is SQL-compatible. It can be a structured text file, e.g. XML if we implemente that. We already have MS Access migration driver, and it does not use SQL for querying about structure or data - mdbtools call are used instead. Thus we were able to reimplement the tableNames method completely.

Kexi - "MS Access for Linux" ... and Windows
© 2002-2007 Kexi Team
This content is available under GFDL
Last edited: January 18, 2008 by js, visited 0 times.