At this point the resource is essentially a drop-in replacement for MySQL-async if you don’t wish to use the exports directly; let me know if you encounter any issues that aren’t by design.
This update resolves nil parameters being undefined and resulting in failed queries, so you can enjoy inserting null into your tables til your hearts content.
Think I know the cause and it’s related to the fixes for nil parameters; looking into a fix now.
Update: v1.6.2
Resolved a regex error when parsing queries containing unescaped JSON strings.
The only known instance of this is with ESX Legacy’s bulk SavePlayer function; basically it would attempt to resolve entries in JSON as though they were named placeholders.
Allow queries containing named placeholders to send nil parameters in cases where there are only nil parameters.
idk what am i doing wrong here but , i installed based on docs but still i get error like : SCRIPT ERROR: citizen:/scripting/lua/scheduler.lua:1155: No such export scalar in resource oxmysql
I couldn’t tell you why there are empty prints, because every time it triggers a print it includes a message and the invoking resource; I’ve not experienced any other behaviour.