Quote:
Originally Posted by PrototypeGaming
If the blowfish.dll error scared them, I wonder what their reaction will be when the solution for it is to download a 3.3 GB file. This source does not deserve to be in the "hands" of lazy leechers. Those that want to set this up and progress it need to spend their time. The solution is out, but people are too lazy to search for the torrent.
Also, I noticed that this source has countless amount of unused variables/methods/parameters. I guess it won't really slow down the server since it isn't being used, but it is still garbage being sent.
|
What method are unused? If there's unused code it's likely code not implemented myself (i.e. by Andy or Ultimation). The down side is when I work with a team, I tend to only use my own work, or recode things.
Quote:
Originally Posted by Ian*
Only advantage to using a text file is you don't have to add another reference to your code and make a connection to mysql LOL
Tbh ini file is ghetto. I think it should really only be used as a temporary storage method, and not store your whole "database" in plain text.
Once it grows larger you will notice the slow downs.
GG Arco. Rage quit. Die by alistar bot and ryze bot ganking you #10
Edit: i think there's even threads about this already.
Anyways, if you think MySQL is to blame for any errors or slow downs, usually it is your fault, not mysql's. If you have any issues like that you can just monitor queries and see which one is bogging you down and using up a lot of your CPU, and FIX IT.
MySQL is like HDTV, text files are like.. not hd.
|
I really didn't think you'd buy into this crap. An INI file will not "slow down" as the database "grows larger". The database is SEVERAL INI files. If it was a single file, your point would be valid.
Quote:
Originally Posted by Ian*
[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
Anyways, MS SQL really only takes the cake when it comes to doing really fancy queries, like ones with multiple functions, joins, subquereies etc etc...
even if mysql seems a little slow, no point in changing to ms sql, its normally a hardware problem from what I've read. I never had any trouble with it being slow myself though :P
|
In my opinion, MSSQL > MySQL.