Yeah, you're sort of right - I wasn't getting the error reported for the
initial failure, which was causing me pain. My logs aren't really up to
scratch we're using docker with AWS and it's a PITA at times.
I'm still not sure what was causing the original problem, but with some
extra work it
On Monday, March 6, 2017 at 10:21:37 AM UTC-5, Mike Bayer wrote:
>
> a ROLLBACK is occurring which suggests a different error has occurred
> and is being swallowed - the transaction can then not continue. Does
> your production environment have logs which would illustrate other
>
a ROLLBACK is occurring which suggests a different error has occurred
and is being swallowed - the transaction can then not continue. Does
your production environment have logs which would illustrate other
exceptions and reasons for rollbacks prior to this one? It is possible
that
Hi, I'm having some trouble with sqlalchemy and timestamps
I have a schema which looks like this
class MyTable(Entity):
__tablename__ = "MyTable"
id = Column(Integer, primary_key=True)
tstamp = Column(DateTime, nullable=False)
when I run a query such as
current_time =
