Apache OpenOffice (AOO) Bugzilla – Issue 64478
oobase crashes on each record insert to a postgres db through ODBC
Last modified: 2006-05-31 14:29:06 UTC
On a Fedora Core 4 system with the following versions: postgresql-odbc-08.00.0100-1 unixODBC-2.2.11-3.FC4.1 qt-ODBC-3.3.4-15.4 unixODBC-kde-2.2.11-3.FC4.1 openoffice.org-core-2.0.1.1-5.1 postgresql-8.0.7-1.FC4.1 Begin with a postgres database that has a single table (ptab). The table has three fields, setup as follows: CREATE TABLE ptab ( tadtest_id integer DEFAULT nextval('"ptab_tadtest_id_seq"'::text) NOT NULL, tadtest character varying(50), tadsecitem character varying(15) ); tadtest_id is a SEQUENCEd number. [I will attach a dump and script to load the database, .odbc.ini, and the testingdb.odb I used. Also I will include my firstInsert.txt and secondInsert.txt crash info files] ODBC is setup with a .odbc.ini. Method for problem replication: 1) oobase ~/testingdb.odb> firstInsert.txt 2>&1 2) select Tables 3) double click ptab 4) click in tadtest field 5) type "test" 6) press tab 7) type "test" 8) press enter 9) capture crash info. 10) oobase ~/testingdb.odb> secondInsert.txt 2>&1 11) click "start recovery" 12) select Tables 13) double click ptab 14) click in tadtest field for a new record (i.e. create record 2) 15) do steps 5-9 again
Created attachment 35780 [details] postgres dump of begining db.
Created attachment 35781 [details] script to load database dump into postgres
Created attachment 35782 [details] the .odbc.ini used to produce crashes
Created attachment 35783 [details] the .odb used to produce the crash.
Created attachment 35784 [details] crash dump from first insert
Created attachment 35785 [details] crash dump from second insert
Sorry, some things I realized I did not get in the inital description. Notes on the database setup. 0) I am assuming you don't already have a postgres database running, because I use the default settings for the ports. 1) the create_testdatabase.sh expects the dump (playdb) to be in /tmp/ 2) the create_testdatabase.sh inserts a couple of aliases at the end of your .profile to start and stop the database (sorry, you may want to remove these after you are done testing). 3) the create_testdatabase.sh creates the postgres db in $HOME/test_db by default. 4) the $HOME/.odbc.ini was all I needed to setup on FC4 to have ODBC work, you will need to replace tdennist with your username in the file. Note on method: 5) when I wrote "2) select Tables" I ment in the Database tab of oobase select the item labled "Tables". Notes on odb: 6) when I attached it, it may have been in a state where it will need "start recovery" clicked when it is first opened. 7) I have gone into Tools->Table Filter, and unchecked everything except ptab, so it is easier to find ptab to test with.
Hi todd, First thanks for this very good bug description. I can reproduce this also on my suse 9.3 linux with a postgres 8.0.1 and OOo m162. I reassign this issue now to the right developer. Bye Marc
Since my last comment, I have found a workaround which makes this a LITTLE more tolerable. IFF you know the next number in the sequence, and enter that into tadtest_id prior to pressing enter (or even before entering the other data), OOo will continue running. However you need to know the next number in the sequence, in my real database for some reason the sequence number and the last number in the _id field are not the same, but I know that problem was created by some of my users.
This issue is identical with issue 64427 and it is already fixed in cws dba203c :-) *** This issue has been marked as a duplicate of 64427 ***
Closing this one