Going for a trot on the Django pony

Post by timtrueman » Tue, Feb 09, 2010, 9:33 PM UTC

johnpaulett wrote: post #5

timtrueman wrote: post #3

Earlier quoted context omitted.

I'm excited for that but what I really meant was split/sharded databases, something you need at scale (which Fluther doesn't need...yet). Correct me if I'm wrong but the upcoming multiple database support can't do that. http://en.wikipedia.org/wiki/Shard_(database_architecture) What it seems to support is "Database Routers" which let you implement your own sharding. It's not that you can't do it. It's just that it do…

I can't find a reference to it, but I recall one of the developers mentioning that the current multi-db support lays the ground work necessary for sharding. I would bet that once 1.2 is released at least several reusable apps pop up that implement various sharding/partitioning strategies.

Post by mrtron » Wed, Feb 10, 2010, 12:43 AM UTC

timtrueman wrote: post #10

mrtron wrote: post #8

Earlier quoted context omitted.

From personal experience, South is not ready. I end up spending 10x the effort using it than writing a few custom queries to add columns or drop a table.

How well would you say you know South? I felt that way at first but once I got to know South I found it to be much better than custom queries.

Post by timtrueman » Wed, Feb 10, 2010, 5:57 AM UTC

sjs382 wrote: post #14

sjs382 wrote: post #2

One of the poster's "cons" was lack of support for multiple databases. Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/

So my comment was deleted from the blog but comments in the vein of "Cool story, bro!" are kept? Definitely not a community I want to participate in again.