Issue 55308 - Key value corrupted on table view
Summary: Key value corrupted on table view
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2005-09-30 16:40 UTC by pikex7
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 pikex7 2005-09-30 16:40:36 UTC 
I have set up a MySQL database with a key field of datatype = INTEGER and
defined it as auto-increment. I then successfully connect in OO RC1, but when I
view the table it shows what looks like overflow in the key field. For example
key field displays as 429496729 (instead of 1)

I then changed the datatype to SMALLINT(5)in the MySQL database and key values
were then as expected. I agree in most circumstances I would use a SMALLINT
field for a key, but I feel that as MYSQL handles this situation perfectly well
there is a defect in OO or the connector. I am using JDBC to connect.
Comment 1 christoph.lukasiak 2006-02-08 15:13:44 UTC 
clu->pikex7: what jdbc driver do you use (vers. number) ?
Comment 2 christoph.lukasiak 2006-03-08 11:03:42 UTC 
does this problem still occure?
Comment 3 christoph.lukasiak 2006-05-08 14:38:57 UTC 
cannot repro that - generally it works fine for me
Comment 4 christoph.lukasiak 2006-05-08 14:40:44 UTC 
not repro, no respond for long time -> close

clu->pikex7: do not hestitate to reopen this issue if still occurs and you have
anything to add