Bug #5136 Geometry objects corrupted when queried

Submitted:	21 Aug 2004 4:12	Modified:	23 Sep 2004 12:42
Reporter:	Peter Yuill	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J	Severity:	S1 (Critical)
Version:	3.0.14	OS:	Windows (Windows XP)
Assigned to:	Alexey Botchkov	CPU Architecture:	Any

Description:
Observed with server 4.1.3.

Geometry objects returned by a client query and then used as a PreparedStatement parameter end up with corrupted coordinate values.

The problem was fixed in 3.1.3, but the current 3.1 source snapshot (20040820) shows the same problem.

How to repeat:
See attached test case.

Test case to reproduce bug

Attachment: GeometryBugReport.java (application/octet-stream, text), 1.85 KiB.

I've tested this both against 4.1.3b on Windows and against 4.1.4 on Linux and can't repeat this bug.

Is there something else I should be testing?

I now see how you _might_ get corruption. The server is returning the _binary_ geometry as plain 'string' types (varchar/char) in the character set of the database (in my case 'latin1'), which is incorrect, because it will go through character conversion in most clients.

The correct behavior would be to return this either in the _binary_ character set, or return it as a BLOB.

I've re-assigned this to the developer responsible for server-side implementation of GIS functionality.

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.