Issue 17909 - Reception of 'serial' data-type completly broken in SO-6 & OO-1.0 ... 1.0.3
Summary: Reception of 'serial' data-type completly broken in SO-6 & OO-1.0 ... 1.0.3
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.3
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-06 06:59 UTC by hpheidinger
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 hpheidinger 2003-08-06 06:59:32 UTC 
SO-6.x thru OO-1.0 ... 1.03 doesn't handle columns of data-type 'serial' and
just groks on it.

      IT WORKED AND STILL WORKS JUST FINE IN STAROFFICE 5.x !!!
      ---------------------------------------------------------  

I still run a copy of SO-5.x in paralell to SO-6.x/OO-1.0.3
I read the comments on this issue that say: "Oh, Postgres is the culprit. Oh,
unixODBC is the culprit. Oh, somthing else is the culprit ...."

No! Someone of the OO people broke the code that handles "serial"s -- at least
for PostgreSQL ...
Comment 1 Frank Schönheit 2003-08-06 10:03:31 UTC 
- major parts of the database access codes have been re-implemented
between SO 5.x and SO 6/OOo 1.0.

- Unless you have are more descriptive about what you're doing and
what goes wrong, this bug is invalid. Sorry, but "doesn't handle" is
not a description anybody can use. At least my glass orb is out of
order at the moment.

- I guess that you may be interested in issue 3872
Comment 2 Frank Schönheit 2003-08-06 10:03:44 UTC 
closing
Comment 3 hans_werner67 2004-02-02 12:58:49 UTC 
change subcomponent to 'none'