I officially dislike sqlite, especially for development.
Published: January 27th, 2007Sqlite looks great by it’s first impressions, but once you dig deeper into your code it can be a real nuisance!
Now, I used to love Sqlite3. I’d tell everyone “It’s so easy to use, you just create your database via a new file, and bam. All you have to do now is tell Rails where the file is, and use the sqlite3 adapter/gem”.
Sure, it was easy until I realized how frustrating sqlite was.
Why? Well, let me just say this. Migrations are impossible with Sqlite. There is very limited support for “adding and removing” columns from an already existing table. Can you already see the frustration during development? Let’s say you have a table “users”, and evenutally you want to add more fields for customization. “Biography, etc.” - Yeah, that’s not possible because sqlite is going to choke on you and give you errors.
SQLite3::SQLException: near “ADD”: syntax error: ALTER TABLE users ADD “biography” varchar(255)
Yep, I was very frustrated when I noticed it wasn’t my code and happening in every app I tried.
So what was my solution? Going back to MySql. Honestly, it’s easier than dealing with limited features.
I have exactly the same problem.
Yeah, so back to MySql eh? :)
Ready. Set. Go.
In terms of the formatting, you're allowed to use markdown, textile, or basic html; it's truly up to you -- what strikes your fancy?
You don't have to worry about your e-mail address being sold to a russian-spam-mafia. I'm only going to use it for my own weird needs; like asking you out for a date on a lonely night of coding.