just implemented the following code:
_saEngine is just the sqlalchemy engine I use.
logging some vars to the terminal window in my routine and this listener,
and I see that this routine is called in the worker after forking.
from celery.signals import worker_process_init
Mike Bayer writes:
> On 01/27/2016 05:32 AM, Lele Gaifax wrote:
>> Here is the diff implementing the third option: it still need to touch also
>> the C implementation, because that does not use the metadata keymap when the
>> key is an integer.
>
> awesome, you're
On 01/27/2016 11:37 AM, Mike Bayer wrote:
>
>
> On 01/27/2016 05:32 AM, Lele Gaifax wrote:
>> Mike Bayer writes:
>>
>>> Let's consider going with the third option I mentioned, I dont think
>>> this will add too much expense if you could test this out please
>>
>>
Lele Gaifax writes:
> Let me know how you prefer me going forward: I can easily try out your (now
> reverted) change, but it's up to you.
The following patch:
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe
If I declare a Sequence at the class level in a model class declaration
using declarative (SQLAlchemy 0.9.10 on postgres), the sequence is not
created by create_all unless the sequence is explicitly associated with a
Column. My use case is a column which stores a URI; if a row is inserted
> On 27 Jan 2016, at 18:59, Chris Macklin wrote:
>
> If I declare a Sequence at the class level in a model class declaration using
> declarative (SQLAlchemy 0.9.10 on postgres), the sequence is not created by
> create_all unless the sequence is explicitly associated
On 01/27/2016 12:57 PM, Lele Gaifax wrote:
> Mike Bayer writes:
>
>> OK my change has revealed a bug in my test suite that wasn't catching
>> that my change fails. The C implementation uses the keymap for
>> integers. Where are you looking that it doesn't ?
>
>
Yes indeed, that does the trick. Thank you!
I would kindly suggest referencing this capability from higher up on that
page. It seems relevant for the section discussing that sequences
associated with a table will be created/destroyed with the table, but this
is the key piece of information that
Mike Bayer writes:
> Let's consider going with the third option I mentioned, I dont think
> this will add too much expense if you could test this out please
Here is the diff implementing the third option: it still need to touch also
the C implementation, because that