On quinta-feira, 1 de agosto de 2013 00:00:54, Constantin Makshin wrote: > While class names and #include-s are certainly safer because they are > checked at compile-time, but text names unleash the real power of QtSql > — unified API (which, IMHO, doesn't make much sense if you stick your > application to one particular RDBMS) and ability to make the database > interface selectable by the final user.
Well, there's a bigger problem here: the Qt SQL backends can be plugins. In order for you to *use* a QXXXXDriver class, you must link to the code that provides the class. If the ODBC driver was built as a plugin (as it usually is), the linking would fail. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
