[ODBC-181] Insert query error decimal + longtext Created: 2018-09-10 Updated: 2018-09-14 Resolved: 2018-09-11 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | 3.0.5, 3.0.6 |
| Fix Version/s: | 3.0.7, 2.0.19 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marek Šrom | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows server 2012 R2 |
||
| Attachments: |
|
| Description |
|
Executing following query: insert into some_table values(-0.0042 ,'please fixed price!!!\r\nAl@1,613.3 EUR/t; drums as usual') in ADODB causes test case & ODBC trace attached... |
| Comments |
| Comment by Lawrin Novitsky [ 2018-09-10 ] |
|
Thank you for your report. Out of sync in 3.0.5 makes me think that was parsing problem. And crash in 3.0.6 may be because (client side) parser chokes on the query. Well, will see. |
| Comment by Marek Šrom [ 2018-09-11 ] |
|
Yes it is not (from my point of view |
| Comment by Lawrin Novitsky [ 2018-09-11 ] |
|
The fix and the testcase have been to pushed to master and odbc-3.0 as 548db71 |
| Comment by Marek Šrom [ 2018-09-13 ] |
|
Thank you, I’ll build from source and test, I have found amother queries with similar problem and will see if it solves all of them... |
| Comment by Lawrin Novitsky [ 2018-09-13 ] |
|
I can only appreciate that! |
| Comment by Marek Šrom [ 2018-09-14 ] |
|
The reported query is ok, unfortunately our application crashes when using ODBC 3.0.6 (it did crash also with the stable release 3.0.6 without this fix)... I applied the fix to 3.0.5, it works ok also for the remaining queries with "out of sync" problem... I try to isolate the problem with 3.0.6 and report a new issue... Thanks |
| Comment by Lawrin Novitsky [ 2018-09-14 ] |
|
So... do I understand correctly that the problem in this report is fixed by the patch in both 3.0.6 and 3.0.5, but you have crash in 3.0.6 not related to this issue? |
| Comment by Marek Šrom [ 2018-09-14 ] |
|
I think so, don’t know the reason of crash with 3.0.6. Keep this issue closed and When I find the problem I’ll open a new one... |