[Qt-interest] Database agnostic programming

[Bill KING]

Partially badly :) There are plans (and work underway) to rectify both
parts of that statement separately.

Jesús Fernández wrote:
> If you use QSqlDriver to write your sql statements this problem is
> partially solved.
>
> On Wed, Mar 25, 2009 at 11:48 PM, Bill KING <bill.king at trolltech.com
> <mailto:bill.king at trolltech.com>> wrote:
>
>     The relevant qt'er is listening and has plans :)
>
>     André Somers wrote:
>     > Hi,
>     >
>     > I am not using PyQt, but it is a very interesting project
>     nontheless! It may
>     > be a serious contender for the future, that might be integrated
>     using Kross
>     > in the future. Currently Kross does not work with Python on
>     windows, but
>     > that may change in the future of course. If it does, then maybe
>     it would be
>     > possible to build some nice interface for use from Qt/C++.
>     >
>     > André
>     >
>     >
>     > "Thomas Dähling" <t.daehling at googlemail.com
>     <mailto:t.daehling at googlemail.com>> schreef in bericht
>     > news:49C975A9.8060707 at googlemail.com...
>     >
>     >> Hi,
>     >>
>     >> in case you are using PyQt you might want to take a look at
>     SQLAlchemy
>     >> (http://www.sqlalchemy.org). I don't know of any such interface
>     for C++,
>     >> even though I'd be highly interested in such a thing as well.
>     >>
>     >> /Thomas
>     >>
>     >> André Somers schrieb:
>     >>
>     >>> Hi,
>     >>>
>     >>> I have build some Qt based software that interfaces with a
>     database. Now,
>     >>> we would like to make the program database agnostic. That is:
>     we want to
>     >>> make it possible to choose a different database as the backend
>     to store
>     >>> the data. While Qt gives me a good way to connect with the
>     different
>     >>> databases, there is no solution for the different SQL dialects
>     that are
>     >>> used, especially for slightly more advanced select queries and
>     for table
>     >>> creation and modification queries. Issues range from different
>     names for
>     >>> data types, different date notations, different characters
>     around table
>     >>> names and values to differences in things like TOP version LIMIT
>     >>> keywords.
>     >>>
>     >>> How do other people solve this issue? Is there some library
>     available
>     >>> somewhere that can "translate" SQL dialects? One option I am
>     looking into
>     >>> is KexiDB, but the page seems a bit outdated so I am not sure
>     what the
>     >>> current status is. Meanwhile, other suggestions are very welcome!
>     >>>
>     >>> André _______________________________________________
>     >>> Qt-interest mailing list
>     >>> Qt-interest at trolltech.com <mailto:Qt-interest at trolltech.com>
>     >>> http://lists.trolltech.com/mailman/listinfo/qt-interest
>     >>>
>     >>>
>     > _______________________________________________
>     > Qt-interest mailing list
>     > Qt-interest at trolltech.com <mailto:Qt-interest at trolltech.com>
>     > http://lists.trolltech.com/mailman/listinfo/qt-interest
>     >
>     >
>
>
>     --
>     Bill King, Software Engineer
>     Qt Software, Nokia Pty Ltd
>     Brisbane Office
>
>     _______________________________________________
>     Qt-interest mailing list
>     Qt-interest at trolltech.com <mailto:Qt-interest at trolltech.com>
>     http://lists.trolltech.com/mailman/listinfo/qt-interest
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>   


-- 
Bill King, Software Engineer
Qt Software, Nokia Pty Ltd
Brisbane Office