You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated to the latest version of DBeaver this morning (Version 22.0.2.202204021640) and since anything that I'm attempting to select from a database with an apostrophe is no longer working when I escape with a backslash.
For example:
select * from table1 where field1 = 'Jo\'s escaped string';
I know I can just change my enclosures to be double quotes and remove the backslash or even use two apostrophes instead of one but sometimes my code is copied from my scripts and it's a hassle to change them over when adding into DBeaver when a backslash should work ok.
Is there any way I can put this escape method back in?
My setup:
Operating system: Windows 11
DBeaver version: 22.0.2.202204021640
Database type: MariaDB (no SSH)
The text was updated successfully, but these errors were encountered:
johamm
changed the title
Escape apostrophe/ single quote with backslash no longer works
Escape apostrophe / single quote with backslash no longer works
Apr 4, 2022
The connection was established as I could run other queries fine. However. this is very odd... I've tried it again today (after the program was closed and my machine has since restarted) and it seems to work now!!!
I updated to the latest version of DBeaver this morning (Version 22.0.2.202204021640) and since anything that I'm attempting to select from a database with an apostrophe is no longer working when I escape with a backslash.
For example:
select * from table1 where field1 = 'Jo\'s escaped string';
I know I can just change my enclosures to be double quotes and remove the backslash or even use two apostrophes instead of one but sometimes my code is copied from my scripts and it's a hassle to change them over when adding into DBeaver when a backslash should work ok.
Is there any way I can put this escape method back in?
My setup:
The text was updated successfully, but these errors were encountered: