I am trying to define relations between persons and teams, however there
are multiple possible relationships (player, reserve, coach, trainer).
My current set up defines both Person and Team using declarative base
classes. For completeness sake; the database is already defined by the
front end,
On Oct 23, 2010, at 11:55 PM, Bertrand Janin wrote:
Hey all,
I'm not sure about the process to submit a patch, so I created a ticket:
http://www.sqlalchemy.org/trac/ticket/1952
Is there any reason why we would keep the current behavior of ignoring
the :port number for
On Oct 24, 2010, at 11:58 AM, sqlalch...@lists.fastmail.net wrote:
I am trying to define relations between persons and teams, however there
are multiple possible relationships (player, reserve, coach, trainer).
My current set up defines both Person and Team using declarative base
classes.
Greetings -
SQLAlchemy 0.6.5 is released. As we approach towards the start of 0.7,
where a good stack of branches are accumulating, the 0.6 series starts to come
in for a landing. 0.6 has been tremendously successful, with 0.6.4 logging
28,143 downloads from Pypi alone over a period of 7
Thank a lot; that did it for me, seems I got very close with the
explicit secondary join statement, but you finished it right off.
Just wanted to take this opportunity to say that I think the Python
community is blessed with both your package, but potentially even more
the effort you put in to
This is amazing work! Thanks Mike. I am truly flabbergasted (heh, I
always wanted to use that word somehow).
How many tests are there?
2010/10/24 Michael Bayer mike...@zzzcomputing.com:
Greetings -
SQLAlchemy 0.6.5 is released. As we approach towards the start of 0.7,
where a good
there are around 2500
On Oct 24, 2010, at 2:48 PM, Alexandre Conrad wrote:
This is amazing work! Thanks Mike. I am truly flabbergasted (heh, I
always wanted to use that word somehow).
How many tests are there?
2010/10/24 Michael Bayer mike...@zzzcomputing.com:
Greetings -
