Issue 54295 - Oracle - numeric results returned from query are formatted as currency by default
Summary: Oracle - numeric results returned from query are formatted as currency by def...
Status: CLOSED DUPLICATE of issue 11746
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-06 22:54 UTC by ctryon
Modified: 2006-05-31 14:29 UTC (History)
2 users (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 ctryon 2005-09-06 22:54:31 UTC 
When using the 2.0 query designer to pull results from an Oracle database,
straight numeric (integer) columns are formatted as currency ($) amounts by
default.  The format of the column can be changed on the currently displayed
result set, but the next time the query is run, the display falls back to
currency again.

This is using the ojdbc14.jar plugin downloaded directly from the Oracle site.

This is probably directly related to the error message that I get when trying to
edit any of the tables: "No type information could be retrieved from the
database.\nThe table design mode is not available for this data source."
Comment 1 eberlein 2005-09-07 09:00:03 UTC 
Is it a duplicate of #43667 and fixed with dba201b?

Peter
Comment 2 ctryon 2005-09-07 13:06:24 UTC 
The problems are certainly related (same underlying cause), but this is more of
an issue of the guessed *display*.  Since there is no valid type information,
the system makes an incorrect guess at how to format the column.  The values are
all straight integer, but for some reason it interprets it as currency.

If the underlying TYPE problem is fixed (I'm not sure what dba201b refers to),
then the display may be a moot point, however it is likely that it will pop up
again in another situation.

(Is this a fix in the OpenOffice code that hasn't made it into Beta2 yet, or a
fix in the underlying Oracle JDBC drivers?)
Comment 3 eberlein 2005-09-08 13:42:04 UTC 
dba201b will be integrated in OO 2.0.1

Peter
Comment 4 Frank Schönheit 2005-09-26 12:12:12 UTC 
searching for "oracle currency" at
http://qa.openoffice.org/issue_handling/project_issues.html easily gives us
issue 11764 and issue 53396.

*** This issue has been marked as a duplicate of 11764 ***
Comment 5 Frank Schönheit 2005-09-26 12:16:43 UTC 
oops, wrong duplicate number
Comment 6 Frank Schönheit 2005-09-26 12:17:23 UTC 
now ...

*** This issue has been marked as a duplicate of 11746 ***
Comment 7 Frank Schönheit 2005-09-26 12:17:36 UTC 
closing duplicate