Apache OpenOffice (AOO) Bugzilla – Issue 27099
openoffice odbc and sqlite on Linux box
Last modified: 2006-05-31 14:29:06 UTC
I've tried to use OpenOffice as a database frontend of sqlite. This is the system i used: Linux Slackware 9.1 OOo 1.1.1rc3, unixodbc 2.2.5 sqlite 2.8.6 sqliteodbc-0.55. the last three compiled from source. Sqlite command line client works well and i can create tables and retrive values with no trouble. odbc comand line client (isql) works well too, both in creating tables and queries. So i've tried to use the Data Source function in OO, setting up the parameters. The problem starts when i try to use one existing table or create a new one. The result is a crash of OOo. The bug is similar to which present in OOo version 1.0, when using mysqlodbc.
Hi, I can reproduce this, however I think it's a driver bug. http://www.sqlite.org/ for the database engine http://www.ch-werner.de/sqliteodbc/ for the odbc driver Bye Marc
> however I think it's a driver bug A crash is always *also* a bug in OOo :)
it is strange that the driver works well with some other procedures. For example i have used the perl module DBD::ODBC and i can write and read data in the sqlite database. I can also retrive some metadata about fields, like num_of_fields, type and name. It's a pity that is not possible to use sqlite from OOo, because sqlite is now the standard php onefile-database, and so it is likely that its use will increase. Do you think it's really not possible to try to fix problems ? I'm trying to use jdbc but i get some uncomprehensible syntax errors (i'll post a new bug issue).
let's evaluate where exactly the crash happens, and if it's really an SQLite problem, and if so, if we can perhaps work around this, before assuming anything :)
Hi filibard, did you send a crash report for this. It would help a lot. Thanks. Best regards, Ocke
problem fixed by the new sqlite-odbc driver. it works perfectly as far as i've tried http://www.ch-werner.de/sqliteodbc/ thank you... ciao Filippo
The sqlite odbc driver was fixed as mentioned by Filippo. Set state to wontfix. Because it is already fix in sqlite odbc code. Best regards, Ocke
Close it