[ODBC-269] BEGIN NOT ATOMIC returning error Created: 2019-11-13 Updated: 2020-01-21 Resolved: 2020-01-21 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | 3.1.4 |
| Fix Version/s: | 3.1.6 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Nigel Gomm | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
32bit windows -> linux hosted MariaDB server (version 10.3.11) |
||
| Description |
|
getting an error from a MariaDB server (version 10.3.11) when my query includes a BEGIN ATOMIC. Query works fine when using mysql ODBC connector 5.3.10 to the same server. BEGIN NOT ATOMIC SET @CONTEXT_INFO ='HP17 # Nigel:::rentman.opendata@21:rentman.finddata@32';select * from misc; END; [10.3.11-MariaDB-1:10.3.11+mariacosmic]You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1 I understood this version of ODBC connector supported composite statements. (Unsure of your priority levels. I made this a blocker because it is preventing me from being able to use this connector at all; and i have other reasons to move away from the mysql connector.) |
| Comments |
| Comment by Lawrin Novitsky [ 2019-11-14 ] |
|
Thank you for your report. It's pity that you didn't file it 1 or 2 days earlier - then the fix could make to the newly published release |
| Comment by Lawrin Novitsky [ 2019-11-15 ] |
|
We've decided that "Critical" is more appropriate |
| Comment by Nigel Gomm [ 2019-11-15 ] |
|
fair enough. any idea of timescales for 3.1.6 ? |
| Comment by Lawrin Novitsky [ 2020-01-21 ] |
|
The fix has been pushed in c114673 commit and will be released in 3.1.6. The release will be published probably today or tomorrow. In any case - soon. |