Hi all
I am now seeing the SQLAlchemy raise 'NoSuchColumnError' occasionally when
concurrent accesses happen with 'select for update'.
My application uses
* SQLAlchemy 0.8.4
* MySQL-python 1.2.3
* CentOS6.7
* python 2.6
* MariaDB 10.0.20 (three-node Galera Cluster with
Sorry for the confusion, I meant "alembic upgrade head" indeed. As you
confirmed the expected behavior, I did a bit of debugging to find out where
I might have done a mistake, and I found the problem.
I wrote a test revision that looked like the following:
def upgrade():
bind =
On 04/18/2016 10:56 AM, bertr...@cryptosense.com wrote:
Hi,
Here's something quite fundamental I don't understand about alembic.
I've initialized my database and created a revision meant to be executed
online. I went like this:
|
alembic init app/alembic
# edit configuration
alembic revision
I try to discourage posts about other projects here only because it is
often the case that the maintainers of those projects aren't being
responsive to user issues, so posting here seeks to take advantage of
the extremely high level of responsiveness we have here. However we
really can't
Hi!
Is it allowed to post questions regarding SQLAlchemy-Continuum's extension
to SQLAlchemy to this group?
I raised related issue at
https://github.com/kvesteri/sqlalchemy-continuum/issues/138
Regards,
Piotr Dobrogost
--
You received this message because you are subscribed to the Google
