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
This seems like a big one; surely I'm not the first to notice this…? But I don't see any mention of it elsewhere in this issue queue… Is it expected that we need to escape apostrophes ourselves?
I was seeing insert queries fail, and I narrowed it down to the failure happening when one of the fields I was trying to insert to contained an apostrophe. By examining the compiled queries, I confirmed that Kuery is not escaping the apostrophe in its compiled insert queries. Here's a sample insert query that caused a failure when I had just a single apostrophe character in the relevant field ("raw") when using SQLite:
I thought it might be just an SQLite thing so I rejiggered my app to work with MySQL. The resulting query is slightly different, but the failure is still there:
Not patching this myself because, one, it's late here and I'm not actually living up to my username very well recently, and two, again, this seems like such an obvious bug that I'm not sure it wasn't intentional…? But if the latter isn't the case, I'll throw something together and make a PR.
The text was updated successfully, but these errors were encountered:
This seems like a big one; surely I'm not the first to notice this…? But I don't see any mention of it elsewhere in this issue queue… Is it expected that we need to escape apostrophes ourselves?
I was seeing insert queries fail, and I narrowed it down to the failure happening when one of the fields I was trying to insert to contained an apostrophe. By examining the compiled queries, I confirmed that Kuery is not escaping the apostrophe in its compiled insert queries. Here's a sample insert query that caused a failure when I had just a single apostrophe character in the relevant field ("raw") when using SQLite:
I thought it might be just an SQLite thing so I rejiggered my app to work with MySQL. The resulting query is slightly different, but the failure is still there:
Here's the code constructing the Insert object:
Not patching this myself because, one, it's late here and I'm not actually living up to my username very well recently, and two, again, this seems like such an obvious bug that I'm not sure it wasn't intentional…? But if the latter isn't the case, I'll throw something together and make a PR.
The text was updated successfully, but these errors were encountered: