18 Jul
2019
18 Jul
'19
10:40 a.m.
On 18/07/2019 15:16, Alan DeKok wrote:
On Jul 18, 2019, at 8:55 AM, Herwin Weststrate <herwin@quarantainenet.nl> wrote:
Meanwhile, Postgresql and Mysql have an option driver_specific_escape that uses driver specific escapes and should fix the problem. It was introduced pretty recently, so I guess 3.0.19 should have it available. (Other drivers can be rewritten to include a specific include as well, it's just that nobody ever did that).
That's the best approach for v3.
How about stored procedures?