If you had a CMS, would you use MYSQL, Sqlite or textfile?

I heard text file is super fast?

MySQL ftw

But, whats the fastest?

quote:

---

Originally posted by john-t
But, whats the fastest?

---

MySQL is a service, it allows multiple connections at once, is easy to manage,... Seriously, if you learn how to use MySQL in PHP, you won't EVER want to use *.txt files anymore!

Imagine two almost simultaneous attempts to write to a single text file to update some stuff. The first instance reads it, then the second does. The first one writes some stuff to it, but the second one overwrites it without knowing that the first instance just wrote something else to that file. Thus, your first writing action will be lost. On a small server, this may not sound like a big problem, but imagine having a popular site with lots of visitors... then you'll be happy you've chosen for MySQL!

Don't know much about SQLite, but if Wikipedia is correct, it uses a .sqlite file to store the information in... Uh?

Yeah, or a .db. I can't have MYSQL know so its txt or db?

I've moved into MySQL / PHP development stuff now, very good definately MySQL!

Saving data to a plain text file is never desirable for a website, like Mattike said, it creates a lot of potential problems.

SQLite is great mostly for applications because it doesn't use a separate process to run in, instead it's called from libraries in the program itself (Firefox uses SQLite). For webservers you won't need a selfcontained solution, MySQL is widely supported, a lot of PHP scripts won't support anything else than MySQL.

So out of txtfiles and Sqlite i should use sqlite, right?

Exactly.