Mysql or Ini?

[_tao4229_]

MySQL vs Windows Ini? Probably neither.

Managed database vs managing my own - Depends on the situation.

[killersub]

MySQL All da wayyyyy!

why?
because it's perforamance system along with its wonderful database storage capacity is just magnificent. in my opinion MySQL has a faster save/load than flat file databases. IN MY OPINION.

[Ian*]

Originally Posted by ☆★Zuper★☆

Now don't say ini is less then mysql.
My 2d mmo, is running on ini and it won't run more smooth if i change it to mysql.
ini can be same good as mysql as long you know what your doing.
All thought mysql is easier for websites with databases etc.
Is just like the discussion for wich programming languages, thats best.
Like C++ or C#?
None of them are.

Okay for the first bold line, mysql is for a database, I'm assuming that's what your ini files are a substitute for?

Some languages are more efficient than others. MySQL may take a bit longer at initial connection but after that lookups would probably be faster and it keeps everything in a neat, organized way (unless you throw together some sloppy database)

Anyways, in my opinion... ini files shouldn't be used for a database lol. that's not their function.

ini files are really just like configuration files... used for storing settings.
MySQL is more for storing large amounts of information.

If you had a server with 1k people on it, and had all of their information stored in an ini file, it'd take forever (not really that long, but for a computer it's slow) to open up an ini file, read all the text, look up information etc... while mysql can just go straight to what your looking for, with same connection time each time, reguardless how big it gets (to an extent)

[dowhatuwant]

Originally Posted by Ian*

Okay for the first bold line, mysql is for a database, I'm assuming that's what your ini files are a substitute for?

Some languages are more efficient than others. MySQL may take a bit longer at initial connection but after that lookups would probably be faster and it keeps everything in a neat, organized way (unless you throw together some sloppy database)

Anyways, in my opinion... ini files shouldn't be used for a database lol. that's not their function.

ini files are really just like configuration files... used for storing settings.
MySQL is more for storing large amounts of information.

If you had a server with 1k people on it, and had all of their information stored in an ini file, it'd take forever (not really that long, but for a computer it's slow) to open up an ini file, read all the text, look up information etc... while mysql can just go straight to what your looking for, with same connection time each time, reguardless how big it gets (to an extent)

Now I also doubt peoples will sotre all chars in 1 file.
Well, your right with that mysql can store it fast like that, but you could make ini do the same, if u sorted our somekind of program.
MySQL is made for databases thats true, but you can work with ini databases as well.
At some points I like mysql better, then ini.
At some points I like ini better, then mysql.
I haven't got problems with loading/saving at ini yet with slow load and so.

But If he wants ini or MySQL, is up to him self

[Korvacs]

You can adapt most things to do other things, but that doesnt mean its efficient when your finshed with it, having to iterate through a folder, checking every filename to find the right character, then loading that data, then iterating through the file untill you find the peice of information you need, simply isnt as efficient as querying a dedicated database, its slower and uses more memory.

INI files simply arnt designed to be used for a database, despite what people have said they are just slower and not as efficient. INI has even been replaced for *** sake, its an out dated system.

[_DreadNought_]

Going to use MySQL then eventually once I can write my own MySQL reader from scratch I will move onto MSSQL.

#Request close

[Korvacs]

Gunna leave it open, its quite an interesting discussion.

[µ~Xero~µ]

when ppl talk about INI they just say INI coz of the file extension.

How about you write into a INI file XML content? Is it a INI or xml file then?

I think this topic should not be called INI or MYSQL. I think it should be called FlatFile or MySQL.

Doesnt matter wich file extension you have as long as you read/write efficently

[Korvacs]

Originally Posted by µ~Xero~µ

when ppl talk about INI they just say INI coz of the file extension.

How about you write into a INI file XML content? Is it a INI or xml file then?

I think this topic should not be called INI or MYSQL. I think it should be called FlatFile or MySQL.

Doesnt matter wich file extension you have as long as you read/write efficently

Good point, however your still itterating through folder structures and files, and then itterating through text to find the data you need, its simply less efficient.

[µ~Xero~µ]

Is it really noticeable? Today´s Servers use RAID-0 / RAID-1 on 10.000 RPM HDD´s, or even Hybrid HDD´s.

I believe you if you say there are speed differences, but as far as technology is today, it wont make too much difference.

Edit:

Well i dont just believe you.. Its a fact. But arent Databases just binary files? :O

[Korvacs]

Originally Posted by µ~Xero~µ

Is it really noticeable? Today´s Servers use RAID-0 / RAID-1 on 10.000 RPM HDD´s, or even Hybrid HDD´s.

I believe you if you say there are speed differences, but as far as technology is today, it wont make too much difference.

Edit:

Well i dont just believe you.. Its a fact. But arent Databases just binary files? :O

Yes they are just binary files, but i assure that the lookup a SQL server performs on the binary file is significantly faster than the lookup that the standard 5165 server performs.

SQL would be out of the job if anyone could just write a simple binary search and beat them on speed.

[Ian*]

Originally Posted by µ~Xero~µ

Is it really noticeable? Today´s Servers use RAID-0 / RAID-1 on 10.000 RPM HDD´s, or even Hybrid HDD´s.

I believe you if you say there are speed differences, but as far as technology is today, it wont make too much difference.

Edit:

Well i dont just believe you.. Its a fact. But arent Databases just binary files? :O

Well even with all this new technology arising, if you were to have thousands, or even millions of things which you needed to store in a database of some kind MySQL would be much more efficient due to the fact it knows what it's looking for and where it is at.

It doesn't have to read every single thing in the database to find it.

Here's a crappy diagram i drew

[dowhatuwant]

Originally Posted by Ian*

Well even with all this new technology arising, if you were to have thousands, or even millions of things which you needed to store in a database of some kind MySQL would be much more efficient due to the fact it knows what it's looking for and where it is at.

It doesn't have to read every single thing in the database to find it.

Here's a crappy diagram i drew

I like drawing.
anyways, the point is right, but if u didn't put explanation on the picture for mysql tabel, then it would look more junk, then ini, but with explanation it makes alittle sense.

[.Beatz]

Originally Posted by pvp99

ini is easier

It depends, I find MySql much much easier than ini as it is better laid out. Some people might find ini easier. It depends on your style and what you are used to.

[bone-you]

Database > flat file, MSSQL > MySQL

Both are performance and overall use.

Flat file will never come close to something like SQL. SQL is like using pointers where flat file is like iterating through an entire string for what you need. Doesn't matter if it's "easier to use" or you think it's "better", if it is data that will be accessed VERY often, you are only hurting your server's performance going flat file.