On Jul 10, 4:29 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On Jul 10, 8:37 am, Ste stefan.aeschbac...@gmail.com wrote:
Hello Group,
I see the following behaviour which I can not explain (don't know
sqlalchemy too well though):
I have the following table setup (heavily
I've managed to fix it using sqalchemy.orm.outerjoin in conjunction
with query's select_from function. Out of interest, why is the naming
scheme different for these 2 functions?
which two names/functions are you referring to ?
outerjoin and select_from, one seems to be lower case, the
I was trying to add an AttributeExtension to a property from my
MapperExtension but I get this error when trying to access the
property:
AttributeError: 'Mapper' object has no attribute '_props'
Here's a test case:
from sqlalchemy import create_engine, Column
from sqlalchemy.ext.declarative
Ah, it's pretty clear why this happens in Mapper.__init__:
self._configure_extensions()
self._configure_class_instrumentation()
self._configure_properties()
Should MapperExtensions that want to extend properties mess with
mapper._init_properties instead?
On Jul 11, 2:49 pm, Nikolaj
thanks Michael. I took a look at README.unittests, but had some
difficulties running them with ironpython (ipy setup.py test fails, and
nosetests.exe doesn't allow you to specificy an interpreter). Still, i
found some help on the interwebs, as well as in the nose __init__.py.
eventually i was
On Jul 11, 2010, at 5:39 AM, Ste wrote:
What I still don't understand is, that if I run the same query in pdb
immediately after the raise, I get back
None (which is what I would expected).
I seem to recall MySQL had some bugs with joins, this log output definitely
looks like one:
SELECT
On Jul 11, 2010, at 5:40 AM, Daniel wrote:
I've managed to fix it using sqalchemy.orm.outerjoin in conjunction
with query's select_from function. Out of interest, why is the naming
scheme different for these 2 functions?
which two names/functions are you referring to ?
outerjoin and
On Jul 11, 2010, at 9:56 AM, Nikolaj wrote:
Ah, it's pretty clear why this happens in Mapper.__init__:
self._configure_extensions()
self._configure_class_instrumentation()
self._configure_properties()
Should MapperExtensions that want to extend properties mess with
On Jul 11, 2010, at 10:04 AM, Harry Percival wrote:
thanks Michael. I took a look at README.unittests, but had some difficulties
running them with ironpython (ipy setup.py test fails, and nosetests.exe
doesn't allow you to specificy an interpreter). Still, i found some help on
the
Hello,
after more then one year of development the sqlalchemy-migrate
development team is proud to announce the release of
sqlalchemy-migrate 0.6. This is the first release of
sqlalchemy-migrate that supports SQLAlchemy 0.6 and firebird
databases.
This release introduces a few backward
10 matches
Mail list logo
