When I moved over from Dreamhost to Slicehost, one of the (minor) motivators was the option to use something different than MySQL. Don't get me wrong, though: MySQL is a nice system, fast, relatively memory-efficient and so on. But what drove and still drives me nuts is that not every storage engine within MySQL supports transactions. MyISAM can be as fast as it gets, if it lacks transaction support, I won't use it for at least some of my tables. And having to manually check that every time I write a new app really started to annoy me. But how to move a site like this, that is using Django, from one database system to another (or to be specific, PostgreSQL in this scenario) as simply as possible?
Read more about "Move a Django site to PostgreSQL: check" ...Archive for [<Tag: postgresql>]
-
Move a Django site to PostgreSQL: check
-
Multiple Tracs with the Same User Database
For my master thesis I'm working with a couple of other people on quite a big project which consists of multiple sub-projects. To get some order into the whole process and documentation we are about to use Trac, the free project management tool by the folks at edgewall. It simply let's you handle one project per instance with its own SVN repository and user base. But what if you want to have multiple instances with the same users but just different permissions per instance?
Read more about "Multiple Tracs with the Same User Database" ...
