Bug #29814 SQL_LONGVARBINARY corrupted on database insertion
| Submitted: | 16 Jul 2007 2:53 | Modified: | 28 May 2013 8:38 |
|---|---|---|---|
| Reporter: | Pascal Janse van Vuuren | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | 3.51 | OS: | Windows (XP SP2) |
| Assigned to: | CPU Architecture: | Any |
[16 Jul 2007 2:53]
Pascal Janse van Vuuren
[30 Jul 2007 8:10]
Tonci Grgin
Hi Pascal and thanks for your report. I suspect you have charsets miss configured somewhere so please: - Attach full test case showing this problem (preferably not using DSN) - Attach my.ini/cnf file from your server - Attach DDL / DML statements needed for your test - Add info on MyODBC / MySQL server used We are aware that MyODBC 3.51 is still not fully capable of handling MB charsets especially on retrieval but with all info provided I might be able to help you work around this.
[30 Aug 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[28 May 2013 8:38]
Bogdan Degtyariov
Cannot continue without feedback from the reporter. The bug is closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.337 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.