So currently i run 3.2.3 essentials with a couchdb server to handle my datatables. With future updates moving the core files of fivem to mysql what will that mean to the guys using couch? will our servers stop working? a bit confused on what the future will be? Will the future Five M be able to save our data or will we need to switch back to sql?
CouchDB is accessible via HttpPerformRequest, it’s still in FxServer. So you will have to update essential to 4.0. That’s all
EDIT : It’s not the future of FiveM. But your future… --’
1 Like
Unrelated to FiveM. Everything will continue as is.
yeah but what im wondering is when sql becomes the base of fivem will the people using couchdb be able to use sql based modds again for their servers without having to jump through hoops and ladders
What the hell are you talking about? The FiveM server does not and will not use any database system by itself, everything else is the community doing random shit without any thought.
2 Likes
A hundred times this. The fact CouchDB was the solution in the first place is… astounding.
I ask because ive been getting a lot of mixed information. so if someone would like to have a clear answer that would be awesome 
Lol, no. They will need to figure out how to mix and match the two. Ultimately SQL will end up winning in the end due to the sheer scalability of it.
cool thanks ive been wondering which one will win and more people seem to be sticking with sql
Whether resources use CouchDB, MySQL, or whatever else, it doesn’t effect what FiveM does. Both CouchDB and MySQL uses have been made by people in the community, not by the FiveM development team.
Choosing whether you want to use CouchDB or MySQL is completely up to you, both will work fine (if used correctly)
Afaik, CouchDB was used as the previous version of Essentials used a Synchronous MySQL library which caused issues with servers locking up when lots of data was being transferred at once.
Now, a person has made a resource which lets you use MySQL with support for Asynchronous, which allows data to be transferred at the same time without locking up. So if you’re seeing resources say they have MySQL Async support, its probably because they are using that resource.
The resource Essentials, which is what you have mentioned, moved to CouchDB using Asynchronous HTTP commands before the resource for MySQL Async came out, which solved the issue with the older version with MySQL. Whether the creator decides to move to MySQL with the Async resource is up to him. But because its a public resource, if you have the skills, you can make it compatible with MySQL Async yourself.
My explanation of the two MySQL versions may not be 100% correct, but afaik thats basically what it comes down to.
tl;dr: Whichever type of database you choose to go with/use has nothing to do with FiveM. Some people think that Essentials is like a “core resource” of FiveM, which is false, its just a very popular resource for server owners.
3 Likes