Migrating an SQLite based django app to PostgreSQL

http://stevelord.tumblr.com/post/86674737/migrating-an-sqlite-based-django-app-to-postgresql

by _b8r0 • 17 years ago

27 13 17 years ago

stevelord.tumblr.com

Rexxar• 17 years ago

It would be very nice to have a "postgreSQLite" with all functionalities of postgreSQL but could be used as sqlite when only one application use the database.

wheels3• 17 years ago

I'm not sure if this is one of the things preventing such, but it's an issue I had with our DB:

When an embedded database is interacting with something like, say, Apache, which uses fork to create multiple processes, your locks have to be multi-process-safe as opposed to multi-thread-safe. For something that's designed with single-process, but multi-threaded access in mind, that can be a bit of a chore.

markessien2• 17 years ago

Is there any difference in the logic? Locking access to a variable will work the same way, even if it's multiple processes trying to access it vs multiple threads. Is the difference just in the mechanism of the lock, or is there some type of difference in behaviour in accessing shared items between threads and processes?

idm3• 17 years ago

The biggest problem I have with developing on SQLite is the limited capacity to perform DB schema migrations. I use South.

SQLite doesn't provide much by way of schema changes, at least not in a manner that the Django ORM can make use of. I just run Postgres locally now, because I can be confident that any migrations I test locally will work on the production system.

tk999• 17 years ago

sorry for the stupid question. Why people use PostgreSQL instead of MySQL? Pros and Cons?

idm3• 17 years ago

ACID: Atomicity, Consistency, Isolation, Durability

See ma.gnol.ia for an example of what can happen with a DBMS that doesn't provide this. That's a big reason why I use Postgres instead of MySQL. With Postgres, the database won't get corrupted by a partially complete operation.

On the other hand, MySQL gets better performance by skipping the whole ACID part... so if you are willing to work with this (i.e. you have a good disaster recovery strategy) then you can theoretically handle a higher load by using MySQL.

teej• 17 years ago

ACID isn't an excuse to skip redunancy and backups.

Migrating an SQLite based django app to PostgreSQL

Related Stories