Re: [sqlalchemy] possible bug in InstrumentedAttribute.__delete__?

2013-07-14 Thread Wichert Akkerman
On Jul 13, 2013, at 22:59, Michael Bayer mike...@zzzcomputing.com wrote: The original intent of default for Column is that it acts exactly like server_default, except it runs on the Python side for the case that your schema wasn't created with this default, or the functionality of your

Re: [sqlalchemy] possible bug in InstrumentedAttribute.__delete__?

2013-07-14 Thread lars van gemerden
Now i was doing both, but you're right, i can remove the default from the column definition, and just initialise the object with the default in __init__ (from metadata i created elsewhere, but will remain available). Setting the default ASAP (on object creation) seems like the way of least

[sqlalchemy] Joinedload and duplicate relations

2013-07-14 Thread Paul Johnston
Hi, I've just been debugging a slow running query: products = db.Product.query.options(sao.joinedload_all('variations.channels'), sao.joinedload_all('variations.specifics')).all() The second joinedload_all should just have been joinedload. It was causing variations to be included twice in

[sqlalchemy] 0.7.10 build test failures

2013-07-14 Thread Hans-Peter Jansen
Dear Mike, while building version 0.7.10 on openSUSE build service, I noticed, that there are a bunch of test failures to care about. My SQLAlchemy project: https://build.opensuse.org/package/show/home:frispete:python/python-SQLAlchemy The build logs are located here:

Re: [sqlalchemy] 0.7.10 build test failures

2013-07-14 Thread Michael Bayer
hi Hans - this issue, a missing import that only triggers on certain platforms, has been fixed in all branches since 0.7. But there's no 0.7.11 released planned at this time. - mike On Jul 14, 2013, at 4:46 PM, Hans-Peter Jansen h...@urpla.net wrote: Dear Mike, while building

Re: [sqlalchemy] 0.7.10 build test failures

2013-07-14 Thread Hans-Peter Jansen
Hi Mike, On Sonntag, 14. Juli 2013 17:03:14 Michael Bayer wrote: hi Hans - this issue, a missing import that only triggers on certain platforms, has been fixed in all branches since 0.7. But there's no 0.7.11 released planned at this time. Thanks for the quick answer. Mind pointing me

Re: [sqlalchemy] 0.7.10 build test failures

2013-07-14 Thread Michael Bayer
you can get that right here: www.sqlalchemy.org/changelog/CHANGES_0_7_11 On Jul 14, 2013, at 5:24 PM, Hans-Peter Jansen h...@urpla.net wrote: Hi Mike, On Sonntag, 14. Juli 2013 17:03:14 Michael Bayer wrote: hi Hans - this issue, a missing import that only triggers on certain platforms,

Re: [sqlalchemy] 0.7.10 build test failures

2013-07-14 Thread Hans-Peter Jansen
On Sonntag, 14. Juli 2013 17:38:12 Michael Bayer wrote: you can get that right here: www.sqlalchemy.org/changelog/CHANGES_0_7_11 Thanks, great. That fixed all tests, but this is left still: [ 156s] -- [ 156s] Ran 4075