The problem with sqlite is that now i only want to use sqlite

Meh, it has its uses

It's great for two things:

1. Portability. If you develop an app for client side use, it's a great local storage method. For a small website or service, it's good too. I use it as the persistence method for most of my personal projects.

2. Testing. Functional tests which hit the database are slow — but much faster if they use an in-memory sqlite DB so it can rapidly migrate between states. Prerequisite is that you use an ORM on top of your production DB, or only use a cross compatible subset of SQL.

What it sucks at though is features (it's quite limiting compared to postgres), access control, write performance and clustering options, so please do not consider it as a serious option for a high traffic production website.

Try postgres.

@hateios which part of "i want to use sqlite" did you not understand

@RazorSh4rk don't try anything else ever.

Also never change a column's name. Cause you can't in sqlite.

@hateios i wasnt aware you could do that in other dbms', cause, like, thats why you plan out your database beforehand

Also im usually working with plsql so