All except: SQLite, MySQL, PostgreSQL, i.e.:
- FireBird (http://www.firebirdsql.org/?op=doc)
- ODBC (implementation is stalled - see kexidb/drivers/odbc/ directory, using unixODBC is preferred). It's can be a matter of looking at other opensource code like QtSQL to learn how unixODBC is used, and implement particular functions of the new KexiDB driver.
- MS SQL Server and Sybase (preferably using FreeTDS)
- MS Access (preferably using MDB Tools)
- maybe XBase ?
- any other driver you're interested in
Any developemnt is consisted of following subtasks:
- Initial design (existing drivers can be valuable as examples)
- Tests and optimizations
- Keeping a driver up to date after KexiDB API changes and improvements
Other related tasks
- Integrating of QtSQL with KexiDB (KexiDB is our DB layer, which is (or should be) more generic than QtSQL. On the other hand, Qt SQL has many own drivers and own users, so it would be useful to wrap it inside KexiDB).
- Testing/cleaning up/improving and integrating Client/Server Extension for SQLite databases. We're using SQLite databases but a single file can be safely accessed by a single process, i.e.no concurrency. Look here how it was solved:
- Let's think how to integrate it with Kexi.