My sql suck, its easy to hack <.< i hate IT!
No, just you who cant use it. <.<
I got mysql, nobody can hack me. I havent done anything else than putting a password to my phpmyadmin and using a secure homepage. (AFS-CMS)
My sql suck, its easy to hack <.< i hate IT!
My sql suck, its easy to hack <.< i hate IT!
No, just you who cant use it. <.<
I got mysql, nobody can hack me. I havent done anything else than putting a password to my phpmyadmin and using a secure homepage. (AFS-CMS)
Wouldn't Sqlite be more secure since it can only be accessed through localhost?
And does anyone know how would it work against SQL injections?
For low load websites, SQLite has worked great in our projects. If you're doing an application in C, its API is simply unbeatable. Perhaps its most distinguishing feature is that it pretty much ignores types. This is, in fact, a "feature", and I have found that it gives it flexibility that is lacking in other situations(although, you have to put your dates in very specific formats to get the sort order to come out right...).
For web development purposes, if you're doing a really high load website, you're going to want to use a non-file based database(personally, I prefer PostgreSQL, but sub MySQL, SQL Server, whatever...)
I also can't express just how great it is for desktop apps though. Its great for 95% of the situations you would need to save data in an application in a "file format" of some variety. It make debugging great(fire up the console on the file your app is writing too and watch inserts as they happen). No configuration at all. No mucking about with binary file formats. No XML parsing.
Relating to the previous poster though, the only place you might really even consider both is low load web applications. While I agree that its good to think big, if you're app is likely to be low load for most of its life, you won't regret SQLite. Another case you might consider it for is a web app that interoperates with a "fatter" version on the desktop, you could do your "export/import" between the two using SQLite.