Chris Bornhoft

@quaertym Sorry I've been tied up with other parts of the project. I can make an example repo if you'd like. Though I found the solution to the problem is...

Are there any more details to this issue? We're running into the same problem, only reflections are being found right now. > special context where the standard context breaking techniques...

Hey @kucukaslancan, I'll take a few minutes to add this over the weekend. I don't think it was ever fully implemented into v2. Thanks!

`returning` is not a currently supported method, it's something we can definitely add 👍

Wow that's quite the version upgrade. At first glance, that query should still work as expected. There was great effort made to maintain full backwards compatibility in v2. Let me...

Okay, I've figured out the source of the issue... it's odd to say the least. Certain systems like MySQL allow _nearly every_ character in the current charset to be included...

This would be a MySQL-only feature. It's possible to add, however you can perform the same task with a `DELETE` and `INSERT` query combination. We'll keep this here for if/when...

Thanks for reporting this! This is not a bug, however. `0.00` is a valid table name in MySQL and likely other dialects as well. Should it ever be a table...

Hey @neto737, if you haven't solved this yet, what does the code above produce? I see you're also using a mixture of bound params and value inserts which isn't recommended....

Great to hear! I'm going to reopen this and mark as a potential bug to fix in 3.0. There should be a way to do this without forcing a `Literal`...