Hi everyone,
I'm encountering problems with transactions when using ZODB. On very rare
occasions the primary connection seems to have dumped the transaction
manager before running the request callbacks. As far as I understand the
code, transaction_manager on the primary connection is set to None
OK thanks, I'll try to increase logging verbosity some way. The permission
part is something I've managed to rule out :/
Regards,
Robin
2015-12-16 4:54 GMT+01:00 Jonathan Vanasco :
> Then the only things I can think of are:
>
> * user/permissions error on supervisor
Good point about the debug_toolbar. That might be it. Thanks!
Any other celery examples out there? Especially around scripting requests?
Thanks,
Robin
2015-11-18 22:12 GMT+01:00 Jonathan Vanasco :
> Ok, this use case is somewhat similar to ours... in that it doesn't
>
Fair point :)
I have an application with a ZODB. Some parts of the app will require
complex calculations that will take a really long time to run. After they
finish, they'll want to write something. So i essentially imagine something
like this:
- Pyramid frontend, read access
- Celery long
Hi,
I'm just curious of what the preferred method of doing changes to a schema
would be?
Usecase:
base_package has the schema:
class BaseSchema(colander.Schema):
some field = etc...
Another package is a plugin, and would like to add a field to that schema.
At least in my head, this would