Bug 192403

Summary: oobase crashes on record insert to a postgres db through ODBC
Product: [Fedora] Fedora Reporter: Todd Denniston <todd.denniston>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://qa.openoffice.org/issues/show_bug.cgi?id=64478
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-23 15:07:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Todd Denniston 2006-05-19 13:45:42 UTC 
Description of problem:
When a record is inserted in a table that is accessed through ODBC and has a
primary key in it, if the PK is not filled in by the user oobase crashes.

Version-Release number of selected component (if applicable):
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


How reproducible:
Always

Steps to Reproduce:
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 attached the following on the OOo bugzilla:
 a dump and script to load the database, .odbc.ini, and the
testingdb.odb I used. Also included 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
  
Actual results:
Crash

Expected results:
Be ready to work on the next record.

Additional info:
See files inserted in to the OOo bugzilla.
Comment 1 Todd Denniston 2006-05-19 14:17:27 UTC 
Note that AFAIK the proposed fix (attached to OOo bz 64427) dba203c _May_ be in
OOo 2.0.3 acording to 
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fdba203c

but any Fedora that has versions between openoffice.org-core-2.0.1.1-5.1 and the
OOo release 2.0.3 are probably affected by this bug as well. (should this bug be
cloned into FC5 and test/RawHide?)
Comment 2 Caolan McNamara 2006-05-23 15:07:42 UTC 
It'd be nice to be able to backport all crash fixes to all supported releases,
but resources limit that to the most serious and widespread problems.

We'll pick it up in the 2.0.3 release in rawhide/fc6 onwards.