Issue 26637 - retrieving umlaut values from postgresql yields an error
Summary: retrieving umlaut values from postgresql yields an error
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2004-03-17 20:23 UTC by hjakobs
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hjakobs 2004-03-17 20:23:18 UTC 
When trying to retrieve rows from a postgresql database via JDBC, 
I get the error message 

"Result set not positioned properly, perhaps you need to call next()."

Environment:
  SuSE Linux 9.0
  Sun JRE 1.4.2
  OpenOffice 1.1.0
  PostgreSQL 7.3.4
  pg73b1jdbc2.jar

To reproduce:

Create a database connection using JDBC to your postgresql database,
which contains a table with umlaut values (like "Müller" for instance).
Press F4 while viewing some document to see the data sources. Select
the database and then the table with the umlauts.

The rows will not show - instead you get the above mentioned error
message. After changing "Müller" to "Mueller" (using psql), everything
works fine again.
Comment 1 marc.neumann 2004-03-26 12:33:55 UTC 
hi,

I can't reproduce this.

I have no problem with this latest posgres driver pg73jdbc3.jar. Please test if
this also happend with this driver and and OOo 1.1.1RC.

Bye and thanks Marc
Comment 2 hjakobs 2004-04-11 17:44:29 UTC 
I have downloaded OpenOffice 1.1.1 in German. At first the error
persisted. Then I created a new database with encoding='ISO8859-1',
which corrected it.

So, the error always appears when you try to retrieve umlaut values
(äöüß) from databases with encoding='SQL_ASCII'. This hint should
find its way into the documentation.

The issue can be closed now.

Regards,
Holger
Comment 3 marc.neumann 2004-05-24 13:47:02 UTC 
Hi,

OK, I close this issue now.

Bye Marc
Comment 4 marc.neumann 2004-05-24 13:47:23 UTC 
close