Bug 110595 - OpenOffice fails when I create table using postgresql ODBC driver
OpenOffice fails when I create table using postgresql ODBC driver
Status: CLOSED ERRATA
Product: Red Hat Raw Hide
Classification: Retired
Component: unixODBC (Show other bugs)
1.0
All Linux
high Severity high
: ---
: ---
Assigned To: Tom Lane
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-11-21 11:32 EST by Maxim Dziumanenko
Modified: 2013-07-02 22:59 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-05-12 00:21:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Maxim Dziumanenko 2003-11-21 11:32:18 EST
Description of problem:
OpenOffice crashes when I create table using 
postgresql ODBC driver libodbcpsql.so from unixODBC package

This bug was fixed in unixODBC-2.2.6

Version-Release number of selected component (if applicable):
unixODBC-2.2.5-9

How reproducible:
Always

Steps to Reproduce:
1.Setup datasource using libodbcpsql.so driver in /etc/odbcinst.ini
and /etc/odbc.ini
2.Run OO, in "Data Source Administration" dialog create table using
mentioned above datasource.
3.In "Table Design" create table with several fields, then 
File->Save As
4. See "Welcome to the OpenOffice.oeg 1.1.0 error report"
  
Actual results:


Expected results:


Additional info:
Comment 1 Tom Lane 2004-03-01 19:50:01 EST
I have updated unixODBC to 2.2.8 for Fedora Core 2.  This appears to
fix the cited problem in a quick test.
Comment 2 John Flanagan 2004-05-12 00:21:19 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-128.html

Note You need to log in before you can comment on or make changes to this bug.