Posts: 310
Threads: 88
Joined: Apr 2011
Reputation:
0
What can i use in my new server to save files dini or sql? or idk if can i use another one. Thanks in advance
Posts: 86
Threads: 4
Joined: Sep 2017
Reputation:
0
Use MySQL, its more efficient and easier to manage. You can even make a UCP and connect it to your server via MySQL.
Posts: 180
Threads: 3
Joined: Mar 2018
Quote:
Originally Posted by nnahtann
Use MySQL, its more efficient and easier to manage. You can even make a UCP and connect it to your server via MySQL.
|
that ^^^^
Posts: 9
Threads: 1
Joined: Apr 2017
Reputation:
0
Pretty much what they all said. Having a database with information in it opens up many opportunities to have a user control panel, since you can grab data from the database into the website, not just from within the game. Also learning SQL and how it works will take you a long way, it's not just used here for SA:MP. It's used with any SQL database, and it will really help you in the long run if you take the time to learn it now.
Posts: 279
Threads: 10
Joined: Apr 2015
Reputation:
0
I know you have a background but to put it simply
DINI or any INI file saving system would be as much as efficient as SQL both SQLite and MySQL, both systems would be fast and both systems would be doing the job you wish it to do, if you know what you want and if you know how to manipulate the data properly. Both would do the same nonetheless..
now to explain advantages and disadvantages
DINI or any INI file saving system
Advantage
- Easy to setup
- Knowledge of path and system should be easy to understand
Disadvantage
- Redundancy
- File Errors
- Prone to Corruption
SQL systems
Advantage
- Less Redundancy
- Corruption is a bit less frequent
- And easy to handle
Disadvantage
- Needs a lot of time to understand and learn, the basic and the advance
(If you only use the basic type of using database system then I recommend you do the File System based, or INI based system since database system in basic form would do you more harm than good.)
- Needs a lot of time to setup and completely and correctly finish it without doing more harm to your system
(In other words testing is a must, although both does the same but MySQL has much more functions and things to adjust for you to make it work as much as fast and as harmless to the easy setup INI files)
All in all both systems would do the same nonetheless as long as you know how to manipulate your data to be safe for use, although MySQL has the edge on this, by a mile, knowledge on how to use MySQL is far more diverse than just saving and updating and making it to a perfect system, unlike INI files which is a much less hassle.(This is On My Opinion, although I prefer MySQL than File System, and had gradually learned through most advanced things that can be used to call the system safe than harmful)
A best bet on advice would be try to learn the curve on File System, it will gradually give you a big edge on how fast you would be able to learn MySQL. Without the syntax and function calls both would just be the same on most parts, other than the part where you try to make your system as redundant free as it should be...
Posts: 579
Threads: 5
Joined: Oct 2015
Quote:
Originally Posted by JesterlJoker
DINI or any INI file saving system would be as much as efficient as SQL both SQLite and MySQL, both systems would be fast and both systems would be doing the job you wish it to do, if you know what you want and if you know how to manipulate the data properly. Both would do the same nonetheless..
|
Err... No. INI was meant to be a configuration storage, not a database solution. If you can't/won't learn SQL for some reason, there's NoSQL but I doubt there's a PAWN library for that.
https://en.wikipedia.org/wiki/INI_file
https://en.wikipedia.org/wiki/SQL