Bug 195855 - Can't support MySQL UNSIGNED data type
Summary: Can't support MySQL UNSIGNED data type
Status: NEW
Alias: None
Product: Data Tools
Classification: Tools
Component: Table Data Editor (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-07-09 12:26 EDT by sensou CLA
Modified: 2008-10-09 05:21 EDT (History)
0 users

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description sensou CLA 2007-07-09 12:26:36 EDT 
When I connect to a mysql database. If the table in this database has a "UNSIGNED" column(INTEGER UNSIGNED, SMALLINT UNSIGNED...), and I used Table Data Editor to edit this table, DTP will give me error message: "Cannot edit table. An unknow or unsupported data type encountered for column ***.".
If I ALTER the table, modify the data type of column to non-unsigned, the Table Data Editor works well.
My mysql JDBC driver is mysql-connector-java-5.0.6-bin.jar.
Because the return value of ResultSetMetaData.getColumnTypeName is "INTEGER UNSIGNED" if the column is defined to INTEGER UNSIGNED. Maybe this is conflict to DTP's DB Definition Model.
Comment 1 John Graham CLA 2007-07-10 10:35:47 EDT 
For consideration in Enablement efforts.
Comment 2 Philippe Weber CLA 2008-10-09 05:21:54 EDT 
The current (1.6.1) enablement project for mysql now contains UNSIGNED data type in all MySql versions of dbdefinition project.

So now the Table Data Editor works well with UNSIGNED data type, 
so this bug could be marked as resolved by last DTP release