Interesting. Thanks for the rundown. Looking forward to 1.6.
On Tuesday, May 28, 2013 6:40:28 PM UTC-4, akaariai wrote:
>
> On 29 touko, 01:07, Chris Conover <clc...@gmail.com> wrote:
> > Adding commit_unless_managed() before the get() seems to fix the
> problem.
>
Also, thank you Tom, Christian, Christophe, and Anssi for helping me track
down this problem. Users are now receiving notifications in a timely manner
because of you.
On Tuesday, May 28, 2013 6:07:22 PM UTC-4, Chris Conover wrote:
>
> Adding commit_unless_managed() before the get() seems
() call? It looks like the major change
is using the underlying database's autocommit mode rather than emulating it
in the ORM. I suppose I'll have to test...
On Tuesday, May 28, 2013 5:43:31 PM UTC-4, Chris Conover wrote:
>
> I bribed the DBA to turn on the general query log briefly
quickly and if that doesn't work, I'll post the full query trace.
On Tuesday, May 28, 2013 5:27:36 PM UTC-4, akaariai wrote:
>
> On 28 touko, 22:20, Chris Conover <clc...@gmail.com> wrote:
> > Well, you can inspect the object and see it's primary key. Surely that
> > means the
, Christophe Pettus wrote:
>
>
> On May 28, 2013, at 1:26 PM, Chris Conover wrote:
>
> > # no middleware that does any writes
>
> Are you using the Transaction Middleware?
>
> --
> -- Christophe Pettus
>x...@thebuild.com
>
>
--
You receiv
Isolation levels or whatever shouldn't matter in my mind, the SELECT is
happening after the COMMIT. Do any of those assumptions strike you as wrong?
Chris
On Tuesday, May 28, 2013 3:43:38 PM UTC-4, Christophe Pettus wrote:
>
>
> On May 28, 2013, at 12:20 PM, Chris Conover wrote:
>
>
> commit before the SELECT?
>
> On May 28, 2013, at 10:52, Chris Conover <clc...@gmail.com >
> wrote:
>
> It's not really feasible to move this project to PostgreSQL.
>
> I honestly just don't understand the problem. According to the Django
> documentation, the O
, May 28, 2013 1:33:10 PM UTC-4, Christophe Pettus wrote:
>
> In the meantime, you can use this:
>
> https://github.com/Xof/xact
>
> On May 28, 2013, at 10:29, Chris Conover <clc...@gmail.com >
> wrote:
>
> That seems to only be available in the dev ve
nseRedirect(reverse('view', {'pk': obj.id}))
>> and i never run into any exception
>>
>>
>> Am Dienstag, 21. Mai 2013 23:20:53 UTC+2 schrieb Chris Conover:
>>>
>>> Calling transaction.commit() after object.save results in
>>> a TransactionMan
object. I'm assuming the view and workers are separate
transactions since I don't see how they could be connected -- though I'm
looking into this.
On Tuesday, May 21, 2013 1:05:54 PM UTC-4, Tom Evans wrote:
>
> On Tue, May 21, 2013 at 4:23 PM, Chris Conover
> <clc...@gmail.com>
>
Hello,
I'm having an issue looking up objects immediately after they are saved and
am wondering if anyone has any advice on how to address the problem.
Specifically, I'm saving an object in a view (nothing fancy, a simple
save()) and then kicking off a Gearman task to do some operations on
11 matches
Mail list logo
