Is a database controlled by .ini files a big risk? With websites of course. I'm just questioning the main advantages of going with mysql. I'm starting to need values saved and retrieved in my current website and I find .ini files easy to work with, but I'm wanting to learn mysql as well. But yea, for things like download counter, rating systems, and log in systems.
I've tried talking to people on website forums, but no one is ever active on those things and to be honest, I find more help from 64d with every problem I have whether it be game design or deciding what to eat. You guys are always a big help to me. I appreciate it. So if anyone can help me out here with a few new systems, let me know. Currently I use .ini files because that's what I was familiar with. I used .ini files in game maker all the time for stuff like this. But now I'm wondering if it's "that bad" of a thing to approach my website needs with the same strategy.
Wouldn't these ini files be visible to the public?
Go for SQL simply because it's faster.
MySQL is so much better than .ini files.
Although I do rather like how old-school .ini files are.
What makes the database so much better? Other than password protection.
Ini files are used as databases? I guess I learned something new today. Though that sounds completely impractical.
I am surprised I didn't say anything like 'ini files!? are you nuts!?'
I must have spaced out or something.Thanks desert fox
ini files are good because they're easily editable by the end user without additional software. Pretty much nothing else. There's no decent reason to use ini files in all but a minority of cases.