| Summary: | MySQL Binary/VarBinary Data Types Improperly Processed | ||
|---|---|---|---|
| Product: | [Tools] Data Tools | Reporter: | David E. Williams <dwilliams> |
| Component: | Enablement | Assignee: | Project Inbox <dtp.enablement-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bfitzpat, legnome57, pierre.queinnec |
| Version: | 1.5.2 | Keywords: | helpwanted |
| Target Milestone: | future | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
David E. Williams
MySQL JDBC Driver: mysql-connector-java-5.1.6-bin.jar As for 195855, current (1.6.1) enablement project for mysql now defines BINARY and VARBINARY datatype. So this bug could be resolved. Hi! I just verified this with the current master, it works.
For future reference, I used:
CREATE TABLE binarytest1
(
id int NOT NULL AUTO_INCREMENT,
name varchar(100) NOT NULL UNIQUE COMMENT 'the name',
date date COMMENT 'a date',
myvardata varbinary(10),
mydata binary(200),
PRIMARY KEY (id)
) ENGINE = InnoDB DEFAULT CHARACTER SET utf8;
The Data Source Explorer view displays everything correctly; the Data > Edit feature works fine; and the Data > Sample Contents correctly displays the test data I inserted.
I'll resolve this as FIXED, please re-open if needed.
Many thanks for the report.
|