check out this case, this is one way to reproduce that:
https://bitbucket.org/zzzeek/sqlalchemy/issues/3532/detect-property-being-assigned-to-more
On 9/15/15 3:56 PM, dewey wrote:
I'll see if I can reproduce this in a simple example.....it's
currently in a job being run every night from a Celery-Beat
scheduler......
Interestingly, just changing the data in the DB made this problem go
away temporarily.......we were seeing this error thrown every night on
staging for 5 days straight,
But after we copied the Prod data into staging, it went away for about
a week.....
This morning, it threw on both staging and prod......first time we've
seen it in Prod....
Thanks for your thoughts...
Dewey
--
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
