Closed Vicken52 closed 2 years ago
Thanks for reporting this issue, it doesn't seems like it compatible anymore.
The differents between those two are the way templates works.
I will fix this in the feature, but for know I recommand to use mysql-async
if you already using it.
mysql-async
--- Example `players`
MySQL.Async.fetchAll('SELECT * FROM `players` WHERE `identifier` = @identifier', {
['@identifier'] = 'steam:...'
}, function(results)
print(json.encode(results))
end)
fivem-mysql
--- Example `players`
MySQL.Async.fetchAll('SELECT * FROM `players` WHERE `identifier` = :identifier', {
['identifier'] = 'steam:...'
}, function(results)
print(json.encode(results))
end)
--- OR
mysql:fetchAllAsync('SELECT * FROM `players` WHERE `identifier` = :identifier', {
['identifier'] = 'steam:...'
}, function(results)
print(json.encode(results))
end)
I'll keep using mysql-async
and wait for the fix before migrating over, thank you so much!
I'm seeing these following errors across all of my resources when trying to startup fxserver with fivem-mysql:
I updated all the resource.lua files with the following changes Is there more that needs to be done to migrate from mysql-async to fivem-mysql that I might be missing?