In case it helps, QSQLiteDriver has a constructor taking sqlite3*
handle. You could open the database with sqlite3_open_v2, then wrap a
QSQLiteDriver instance around it.
Igor Tandetnik
On 5/28/2013 9:49 AM,
[email protected] wrote:
Correct. We must not drop below the Qt interface level.
On May 28, 2013 at 7:29 AM Igor Tandetnik <[email protected]> wrote:
On 5/28/2013 8:05 AM, Roland Hughes wrote:
Your response doesn't say anything useful.
When *WE* tell you the kit required for the project, it is just that, the
kit required for the project. Given the rules and regulations for this
project the kit must be as is without hacks. The target will run roughly 12
years without modification unless a catastrophic bug is found. Given that
such an issue rarely shows up within the first 5 years the rules and regs
require publicly available archives. No personal hacks or desk drawer builds
allowed.
Do those rules and regulations prohibit your application from calling
sqlite3_config(SQLITE_CONFIG_URI, 1), or using sqlite3_open_v2() with
SQLITE_OPEN_URI flag to open the database?
--
Igor Tandetnik
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Roland Hughes, President
Logikal Solutions
(630)-205-1593 - cell
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
