On Tue, Jan 19, 2010 at 11:27 PM, Russell Keith-Magee
wrote:
> On Sat, Dec 19, 2009 at 10:48 PM, Russell Keith-Magee
> wrote:
>> On Sat, Dec 19, 2009 at 1:41 AM, Brett Hoerner
>> wrote:
>>>
>>> I would think read-slaves would be a pretty common application of
>>> multidb, but I can only speak t
On Sat, Dec 19, 2009 at 10:48 PM, Russell Keith-Magee
wrote:
> On Sat, Dec 19, 2009 at 1:41 AM, Brett Hoerner wrote:
>>
>> I would think read-slaves would be a pretty common application of
>> multidb, but I can only speak to our use case. I know it's a bit late
>> in the game, but we'll have to
On Jan 7, 7:33 pm, Russell Keith-Magee wrote:
> then my understanding of your proposal is that the only change is that
> read-slave won't get created under the test setup. But doesn't that
> mean that::
>
> MyModel.objects.using('read-slave').filter(...)
>
> will fall over?
No, not in my ment
On Fri, Jan 8, 2010 at 3:17 AM, Brett Hoerner wrote:
> On Jan 5, 8:09 pm, Russell Keith-Magee wrote:
>> If you're actually doing master/slave in the wild, your guidance may
>> actually be more enlightening than my theoretical navel gazing. In
>> particular - how have you got master/slave configur
On Jan 5, 8:09 pm, Russell Keith-Magee wrote:
> If you're actually doing master/slave in the wild, your guidance may
> actually be more enlightening than my theoretical navel gazing. In
> particular - how have you got master/slave configured? How do you find
> and select slave databases? How does
On Wed, Jan 6, 2010 at 12:42 AM, Brett Hoerner wrote:
> On Dec 22 2009, 4:27 pm, Russell Keith-Magee
> wrote:
>> I'll need to cogitate on this over my Christmas pudding :-)
>
> Did you come to any conclusions, or need any more feedback on the read-
> slave testing issue?
I haven't reached any co
On Dec 22 2009, 4:27 pm, Russell Keith-Magee
wrote:
> I'll need to cogitate on this over my Christmas pudding :-)
Did you come to any conclusions, or need any more feedback on the read-
slave testing issue?
I in no way mean to rush, I just wanted to make sure I didn't (and
don't) miss anything a
Yes, multiple database support was merged into trunk on December 22:
http://www.djangoproject.com/multidb-changeset/
Alex
On Mon, Jan 4, 2010 at 9:40 AM, Joe wrote:
> Has this code been merged to a 1.2 alpha build somewhere or is the
> multi-db branch still the current release? Only asking beca
Has this code been merged to a 1.2 alpha build somewhere or is the
multi-db branch still the current release? Only asking because the
first message in the thread indicated a schedule which meant the code
would be merged in before EOY and I just want to make sure I'm on the
right codebase moving fo
On Wed, Dec 23, 2009 at 1:32 PM, Michael Manfre wrote:
> With multiple database defined, what is the expected behavior for
> syncdb and the other db related commands?
The management commands all work the same way under multidb - they
only ever work on a single database at a time. If you don't spe
With multiple database defined, what is the expected behavior for
syncdb and the other db related commands? The documentation shows that
it is relatively easy to associate an admin form with a given
database, but is there a way of associated a model or app to a given
database?
Regards,
Michael Man
On Tue, Dec 22, 2009 at 4:55 PM, Brett Hoerner wrote:
> On Dec 22, 4:27 pm, Russell Keith-Magee
> wrote:
> > * Allow TEST_NAME=None to mean "don't try and instantiate this
> > database in test mode"
>
> That sounds good, too.
>
If I was using the slaving part of multi-db i'd be very likely to w
On Dec 22, 4:27 pm, Russell Keith-Magee
wrote:
> * Allow TEST_NAME=None to mean "don't try and instantiate this
> database in test mode"
That sounds good, too.
> * Allow a top level TEST_DATABASES setting; TEST_DATABASES would
> override DATABASES; if TEST_DATABASES isn't defined, then TEST_N
On Wed, Dec 23, 2009 at 7:06 AM, Brett Hoerner wrote:
> On Dec 19, 6:48 am, Russell Keith-Magee
> wrote:
>> You're right - read slaves are an intended common use case
>
> I know the branch landed but I'd like to mention another issue
> regarding read-slaves, hope that's OK. :)
>
> Running tests a
On Dec 19, 6:48 am, Russell Keith-Magee
wrote:
> You're right - read slaves are an intended common use case
I know the branch landed but I'd like to mention another issue
regarding read-slaves, hope that's OK. :)
Running tests against code that uses master and read-slaves (but
actually point at
On Sat, Dec 19, 2009 at 1:41 AM, Brett Hoerner wrote:
> I'm not sure if 1.2 intended to fully support read-slaves, but I'll
> post this quick anyway as we've just run into it while trying to
> upgrade at DISQUS.
>
> You might think that having support for multiple databases implies
> that using a
On Sat, Dec 19, 2009 at 3:46 AM, Jani Tiainen wrote:
> Haven't run any tests, but as a small request - I would be very happy that
> you guys take a look ticket #11017 it's quite performance killer to some
> selects on char fields (specially startswith) on Oracle.
This has nothing to do with multi
On Fri, Dec 18, 2009 at 9:43 AM, Russell Keith-Magee wrote:
> Hi all,
>
> This is a second and final call for feedback on the multidb branch.
>
> Barring any objections or the discovery of major problems, my
> intention is to commit this early next week, hitting the alpha 1
> feature deadline by
On Dec 18, 9:50 am, Alex Gaynor wrote:
> I'm wondering if perhaps the most prudent thing to do would be to
> simply remove this check. The end result will be you'll get an
> integrity error on Postgres/Oracle when you try to save (and SQLite
> and MySQL will just let you do whatever).
That would
On Fri, Dec 18, 2009 at 12:41 PM, Brett Hoerner wrote:
> I'm not sure if 1.2 intended to fully support read-slaves, but I'll
> post this quick anyway as we've just run into it while trying to
> upgrade at DISQUS.
>
> You might think that having support for multiple databases implies
> that using a
I'm not sure if 1.2 intended to fully support read-slaves, but I'll
post this quick anyway as we've just run into it while trying to
upgrade at DISQUS.
You might think that having support for multiple databases implies
that using a read-slave would Just Work, and that's mostly true.
There's one ed
Hi all,
This is a second and final call for feedback on the multidb branch.
Barring any objections or the discovery of major problems, my
intention is to commit this early next week, hitting the alpha 1
feature deadline by the skin of our collective teeth :-)
There has been one big change since
22 matches
Mail list logo
