On 4/22/15 12:45 AM, Oliver Palmer wrote:
We're using a Flask extension to work with sqlalchemy called
flask-sqlalchemy. The engine is usually not directly exposed but echo
can be enabled using a configuration var
On 4/22/15 12:45 AM, Oliver Palmer wrote:
We're using a Flask extension to work with sqlalchemy called
flask-sqlalchemy. The engine is usually not directly exposed but echo
can be enabled using a configuration var
On 4/22/15 12:45 AM, Oliver Palmer wrote:
We're using a Flask extension to work with sqlalchemy called
flask-sqlalchemy. The engine is usually not directly exposed but echo
can be enabled using a configuration var
On Wednesday 22 April 2015 14:17:02 Mike Bayer wrote:
On 4/22/15 12:45 AM, Oliver Palmer wrote:
We're using a Flask extension to work with sqlalchemy called
flask-sqlalchemy. The engine is usually not directly exposed but echo
can be enabled using a configuration var
On Monday 20 April 2015 13:24:49 Michael Bayer wrote:
On Apr 20, 2015, at 12:56 PM, Guido Winkelmann guido@ambient-
entertainment.de wrote:
On Monday 20 April 2015 11:23:06 Mike Bayer wrote:
On 4/20/15 8:09 AM, Guido Winkelmann wrote:
On MySQL/PostgreSQL, this line fails:
Apparently,
On Tuesday 21 April 2015 09:43:51 Mike Bayer wrote:
On 4/21/15 6:45 AM, Guido Winkelmann wrote:
On Monday 20 April 2015 21:57:40 Oliver Palmer wrote:
[...]
So I got to thinking about what we're doing differently with sqlite and
this bit of code comes to mind:
# sqlite specific
On 4/21/15 6:45 AM, Guido Winkelmann wrote:
On Monday 20 April 2015 21:57:40 Oliver Palmer wrote:
[...]
So I got to thinking about what we're doing differently with sqlite and
this bit of code comes to mind:
# sqlite specific configuration for development
if db.engine.name ==
On Monday 20 April 2015 19:22:36 Mike Bayer wrote:
On 4/20/15 12:56 PM, Guido Winkelmann wrote:
I just tested, the problem is still present in the current master
(bd61e7a3287079cf742f4df698bfe3628c090522 from github). Guido W.
can you please try current master at least as of
On 4/21/15 11:19 AM, Guido Winkelmann wrote:
On Tuesday 21 April 2015 09:43:51 Mike Bayer wrote:
On 4/21/15 6:45 AM, Guido Winkelmann wrote:
On Monday 20 April 2015 21:57:40 Oliver Palmer wrote:
[...]
So I got to thinking about what we're doing differently with sqlite and
this bit of code
We're using a Flask extension to work with sqlalchemy called
flask-sqlalchemy. The engine is usually not directly exposed but echo can
be enabled using a configuration var
https://github.com/pyfarm/pyfarm-master/commit/5d0abc03273f0fcce3c7d2cf44ef8981dd31aa41
which should
have the same
On Monday 20 April 2015 21:57:40 Oliver Palmer wrote:
[...]
So I got to thinking about what we're doing differently with sqlite and
this bit of code comes to mind:
# sqlite specific configuration for development
if db.engine.name == sqlite:
@event.listens_for(Engine, connect)
On 4/20/15 12:56 PM, Guido Winkelmann wrote:
I just tested, the problem is still present in the current master
(bd61e7a3287079cf742f4df698bfe3628c090522 from github). Guido W.
can you please try current master at least as of
a3af638e1a95d42075e25e874746, thanks.
--
You received this
Hey original developer pyfarm-master here, Guido pointed me at this thread.
I've run a test with a3af638e1a95d42075e25e874746 and the sqlite tests are
still failing to drop the tables:
https://travis-ci.org/pyfarm/pyfarm-master/builds/59341150
Since Guido commented however I merged a PR he
Hi,
Have there been any non-backwards-compatible changes in SQLAlchemy 1.0
compared to 0.9.9?
We are seeing a lot of sudden breakage in our unit tests when switching to
SQLAlchemy 1.0 from 0.9.9. Tests that worked fine before suddenly fail
across the board.
Here's a an example of a test
On Apr 20, 2015, at 12:56 PM, Guido Winkelmann
gu...@ambient-entertainment.de wrote:
On Monday 20 April 2015 11:23:06 Mike Bayer wrote:
On 4/20/15 8:09 AM, Guido Winkelmann wrote:
[...]
On sqlite, drop_all() seems to fail to get the order of table drops
right, and consequently runs
On Monday 20 April 2015 11:23:06 Mike Bayer wrote:
On 4/20/15 8:09 AM, Guido Winkelmann wrote:
[...]
On sqlite, drop_all() seems to fail to get the order of table drops
right, and consequently runs into a referential integrity error.
If you can post a reproducible issue, that's what I can work
On 4/20/15 8:09 AM, Guido Winkelmann wrote:
Hi,
Have there been any non-backwards-compatible changes in SQLAlchemy 1.0
compared to 0.9.9?
Most behavioral changes are listed out at
http://docs.sqlalchemy.org/en/rel_1_0/changelog/migration_10.html; I've
urged everyone to please read through
On 4/20/15 8:09 AM, Guido Winkelmann wrote:
Hi,
Have there been any non-backwards-compatible changes in SQLAlchemy 1.0
compared to 0.9.9?
We are seeing a lot of sudden breakage in our unit tests when
switching to SQLAlchemy 1.0 from 0.9.9. Tests that worked fine before
suddenly fail
18 matches
Mail list logo
