Issue 2134 - crash on ODBC datasource when username not set
Summary: crash on ODBC datasource when username not set
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 638
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ocke.janssen
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks: 2139
  Show dependency tree
 
Reported: 2001-11-06 19:04 UTC by kbrink
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description kbrink 2001-11-06 19:04:04 UTC
Attempting to browse the tables of an ODBC datasource, that was created
without entering anything in the "username" field, causes OO to abort with
an "unrecoverable error". Entering anything (even a nonexistent username)
into the username field prevents the crash.
I am connecting to a PostgreSQL DB with UnixODBC under linux. The problem
happens both in OO 638c and the Staroffice 6 beta.

To reproduce:
(install OO->workstation install; UnixODBC; create ODBC datasource"PostgreSQL")
1) in swriter, choose "Tools | Data sources ..."
2) click "New Data Source"
3) set "Database type" -> ODBC
4) for "Data source url" -> press ".." and choose ODBC datasource "PostgreSQL"
5) click "OK" to create datasource (do not enter anything under the ODBC tab!)
6) now, choose "View | Data sources"
7) expand the new data source
8) expand "Tables"

Actual result:
OO aborts with an "unrecoverable error".

Expected result:
OO should display a meaningful error message (and should not crash!).

My environment:
OpenOffice.org build 638c
Linux kernel 2.2.19; i686 with 128 MB ram;  glibc 2.1.2 (RedHat 6.1)
PostgreSQL 6.5.2  (from RH 6.1)
unixODBC 2.0.9 (from http://www.unixodbc.org/; compiled on RH 6.1)
(contents of /etc/odbc.ini available if you want it)
Comment 1 dirk.grobler 2001-11-07 07:59:41 UTC
Ocke, and maybe Marc may assist you, please have a look at it.
Comment 2 marc.neumann 2001-11-07 10:46:58 UTC
Marc: I can reproduce this issue, with an Postgresql ODBC driver. An 
other driver (mysql) works.
Comment 3 ocke.janssen 2001-11-14 16:52:53 UTC
Hi,
the problem was that the error code was misinterpreted.
The file effected is in
dba/connectivity/source/drivers/odbc/OConnection.cxx.
The newest version.

Regards,
Ocke
Comment 4 ocke.janssen 2002-05-24 10:42:52 UTC
Hi, 
fixed in OOo 1.0

Ocke
Comment 5 ocke.janssen 2002-10-07 08:36:51 UTC
Closing now.
Comment 6 hans_werner67 2004-02-02 12:56:47 UTC
change subcomponent to 'none'