Apache OpenOffice (AOO) Bugzilla – Issue 75290
Access to postgresql database is readonly -- no edit allowed
Last modified: 2013-08-07 15:45:17 UTC
When I access postgresql database (using either jdbc or odbc) the access is readonly --- I can't edit or delete rows. The "Edit Data" button is disabled. Details follow: Cheers, Geoff Russell Ubunto 6.06.1, postgresql 8.1 The following error is in the postgres log. ------------------------------------------------------------ Start error CONN ERROR: func=PGAPI_GetInfo30, desc='', errnum=209, errmsg='Unrecognized key passed to SQLGetInfo30.' ------------------------------------------------------------ End error And also: STATEMENT ERROR: func=PGAPI_SetStmtAttr, desc='', errnum=28, errmsg='Unsupported statement option (Set)' ------------------------------------------------------------ hdbc=138465536, stmt=139330016, result=0 manual_result=1, prepare=0, internal=0 bindings=0, bindings_allocated=0 parameters=0, parameters_allocated=0 statement_type=-2, statement='(NULL)' stmt_with_params='(NULL)' data_at_exec=-1, current_exec_param=-1, put_data=0 currTuple=-1, current_col=-1, lobj_fd=-1 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=3, scroll_concurrency=1 cursor_name='' ----------------QResult Info ------------------------------- CONN ERROR: func=PGAPI_SetStmtAttr, desc='', errnum=0, errmsg='(NULL)' ------------------------------ odbc.ini [testdb] Description = testdb Driver = PostgreSQL Trace = Yes TraceFile = /tmp/psqlodbc.log Database = testdb Servername = localhost UserName = geoff Password = Port = 5432 Protocol = 6.4 ReadOnly = No RowVersioning = No ShowSystemTables = No ShowOidColumn = No FakeOidIndex = No ConnSettings = -------------------------------- odbcinst.ini [PostgreSQL] Description = PostgreSQL ODBC driver Driver = /usr/lib/odbc/psqlodbc.so Setup = /usr/lib/odbc/libodbcpsqlS.so Debug = 0 CommLog = 1
Do you use the primary key? Can you try it with the nwest version 2.2?
Reproducible on Linux with 680m14 with unixODBC 2.2.11-7.1 and postgresql 8.1.8-1 Fedora 6. But the error message seems to be emitted by unixODBC. So I would first investigate on configuring the connection unixODBC <-> postgresql.
does this problem still occure in a current version, available here: http://download.openoffice.org/680/index.html?intcmp=1236
also test dba.openoffice.org/drivers
I can't reproduce this behaviour with the latest JDBC3 driver and postgres 8.2.3 and OOo 2.3.1 for MacIntel OSX X11. Alex
no response -> invalid
-> closed