Ghmattimysql: My MySQL Implementation for FiveM [1.3.2]

FiveM Resource Development & Modding Releases
, , , ,
102

Good work ! the script is great

1 Like
103

Updated (node.js version)

  • The node.js version is now an release candidate. If there are not any feature requests, I will move it to full release in a week from now. Meaning the old C#-based connector will be archived.
  • All kinks with the variable input have been solved.
  • Mostly docs should be missing which I’ll be writing in the next 7 days.

About mysql_connection_string

  • I am also very sorry to announce that a ghmattimysql won’t be able to take a connection string maybe until release. Compared to mysql-async, the resource is ready to go as soon as the exports are loaded, and not when onServerResourceStart fires. But currently Convars cannot be read until these events fire; which would mean awaiting until this has happened, but since you cannot await it on the top level in javascript at the moment, I would have to add an Promise to wait until the pool has been established.
  • I have not decided yet if I want the connection string option in the library, but I am open for convincing.
104

Huh? That shouldn’t be the case and most definitely isn’t.

Maybe ask around before making odd conclusions and posting them publicly as if they’re truth.

105 
console.log(global.GetConvar('mysql_connection_string', 'default'));

will always default unless run after onResourceStart . I added

set mysql_connection_string "hey world!"

this time definetely to the correct server.cfg; although I am on the 760 server version.

106

Just tried it, and you seem to be wrong, even on 760.

Output:

Started resource scoreboard
Started resource playernames
hey world!
Started resource myresource

__resource.lua:

server_script 'hi.js'

hi.js contains your console.log call.

server.cfg:

# ///

set mysql_connection_string "hey world!"
start myresource

Maybe you tried to start the resource before the convar was set? .cfg files aren’t a map of settings, they’re a script file, as evidenced by the fact they’re run using +exec which literally is called exec.

107

idd i am. i put it to the other convars in the server.cfg with the default ones from https://docs.fivem.net/server/#server-cfg which is afaik common practice and way down from the start block. then I am smarter again. thanks a lot.

108

Perhaps the example should be updated to spread resource starts around randomly to highlight this fact. :stuck_out_tongue:

109

Or prehaps I should deal with this issue for ghmattimysql by documenting that the vars belong before the start command.

110

Update

We are now at rc.1, the script now takes convars if they are above the start of the script e.g.:

set mysql_connection_string "mysql://mysqluser:password@localhost/test?dateStrings=true"
start ghmattimysql

and the config.json is missing.

111

Update

Added Additional Configuration Options

1 Like
112

Update to rc.3

execute uses now the standard query, when no prepared statement according to the mysql/mariadb syntax is found. The one with the ?.

This would cause issues and possible slow downs otherwise.

113

great resource :smiley:

1 Like
114

Updated

  • @justcfx2u fixed the old returning friend of the not null from scalars.
  • The old query style is now translated into the new one, so that prepared statements are used.
115

Keep up the great work :muscle:

1 Like
116

Its compatibility with ESX jobs?

117

Definately no. It uses a completely different command set than mysql-async.

To make it work you would have to change the commands one by one.

Also you cannot use it on linux at the moment, for some reason v8 in linux is not garbage collecting properly and executing stuff properly (got freezes on certain sql commands) and out of memory crashes.

1 Like
118

Does this reproduce even if you don’t use outdated server builds but build your own/use the Docker builds?

120

disregard that. I confused folders.

121

Would u say this is faster than Mysql-Async?

122

It is, but it does not matter. The mysql-async node variant is fast enough. It should handle without any issues 1500 queries per second. Whereas most servers run maybe 100-300 or so?