kexi project
Rapid Database Application Development
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
KDE

Member of the Calligra Suite

No Software Patents!

FrontPage/KexiDBDesign/KexiDBDrivers

ODBC Driver

Table of Contents
      Terms
     Main Issues
     Development Hints
     ODBC <-> KexiDB: Redundant & common terms
     ODBC Integration with Kexi / KexiDB / KDE
     External documentation

Document introduced by jstaniek

Terms

We'll use "ODBC Driver" term in these papers, although it is all about developing KexiDB-level driver that is built on top of existing lower-level ODBC libraries, as described below. So, by ODBC Driver we don't mean developing the layer between given database and ODBC protocols.

^ toc

Main Issues

  • There are a few different apporaches for ODBC implementation:

We need to decide which one (unixODBC or iODBC) to use on UNIX. Using iODBC could simplify later intergation on Mac OS X...

  • Motivation for developing the ODBC driver for both targets:
    • For better promotion of migration possibilities from win32 to UNIX in small and middle-sized workplaces and in 3rd party software vendor's market.
    • For easy interoperability of new Kexi applications with software that is locked-in win32 platform. Many businesses are in fact locked-in win32 platform because they rely on given amount of NOT PORTABLE, specialized software.
^ toc

Development Hints

  • Let's look at exisitng software that integrates with ODBC layer. Especially, there is valuable option to see into QSQL QODBC3 driver/plugin's source code, even if QSQL API is just a subset of what KexiDB try to offer.
^ toc

ODBC <-> KexiDB: Redundant & common terms

All things described below need to be integrated and hidden in Kexi API / infrastructure:

  • ODBC has its own drivers, administered via config files or GUI.
  • User DSN - personal Data Sources. System DSN - admin's Data Sources. These need to be integrated with (more generic) KexiDB Connection Data Sources and its GUIs.
^ toc

ODBC Integration with Kexi / KexiDB / KDE

There are few GUIs for administering on ODBC layer. We'll need to think how to integrate these elements with Kexi configuration framework, especially when in the future Kexi would export own configuration GUI as the KDE Control Center Module.

Existing ODBC configuration GUIs are a bit obsolete, not well integrated into KDE framework.

It shouldn't be to hard to introduce generalized config GUI that also covers ODBC configuration. Naming convention can be a bit different (more generic). Existing configuration framework is pretty similar to one what we may need for Kexi.

See also: Dublin/aKademy2006 Discussions about ODBC Support in Kexi and KDE.

^ toc

External documentation



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