On Sep 16, 2:16 am, mrts <[EMAIL PROTECTED]> wrote:
> * generally we should strive for a hassle-free experience so that
> `easy_install django-foo` gives you an expected entry point (`from
> django.apps import foo`) and works-out-of-the-box feel
Just a slightly twisted thought, what if a site's
On Sep 10, 12:53 pm, Simon Willison <[EMAIL PROTECTED]> wrote:
> For those who weren't at DjangoCon, here's the state of play with
> regards to multi-db support: Django actually supports multiple
> database connections right now: the Query class (in django/db/models/
> sql/query.py) accepts a co
> obj = Article.objects.using('master').get(pk = 4)
> obj.name = 'Hello'
> obj.save(using = 'master')
Shouldn't the object remember the database used to fetch it, and
save()
should save it back there?Then you would only have to specify it
like that if you want to fetch it from one database
On May 22, 9:59 am, Simon Willison <[EMAIL PROTECTED]> wrote:
> 1. Replication - being able to send all of my writes to one master
> machine but spread all of my reads over several slave machines.
> 2. Sharding - being able to put User entries 1-1000 on DB1, whereas
> User entries 1001-2000 l
