Hi list,
Here is my solution (thanks to jek from IRC).
# Mappers
channel_mapper = mapper(Channel, channel_table,
properties = {
playlists:relation(PlaylistChannel,
backref=channel,
primaryjoin=and_(channel_table.c.id==
Hi,
On Nov 14, 12:44 am, m h [EMAIL PROTECTED] wrote:
On Nov 13, 2007 5:14 AM, Simon Pamies [EMAIL PROTECTED] wrote:
Hey Simon, I found your code today and started to hack on it to do db
migrations. Since it is out of the scope of your project, I'll
probably just write my own. But before
Hi,
I tried to migrate to SQLAlchemy 0.4 but unfortunately, 0.4 does
not seem to work with the weird table and column names I have
in my legacy database.
I believe this behavior is a regression because the script below
worked for me with 0.3.10. I got something horribly wrong (still
learning
I need to evaluate a third-party application, that will be integrated
with others by one of my programs.
My integration app runs on linux with SA 0.4, and I will strive to use
the latest stable release.
I need to write a couple of requirements to choose the third-party
application.
Will I
On Nov 13, 2007, at 9:17 PM, Chris M wrote:
I didn't see any tickets about this on the trac, so I thought I'd
bring it to everyones attention. Since it's a development version I
wasn't sure if this mattered (or was known about), so if it does I can
draft up a quick test case.
thanks for
Hi moderators,
Could we ban this Riaz M. from sending any more emails to this group?
He also tried to send a lot of spam in TurboGears group and I
moderated and banned him again there.
Regards,
Florent.
--~--~-~--~~~---~--~~
You received this message because you
On Nov 14, 2007, at 11:07 AM, Chris M wrote:
It's quite simple actually, there is absolutely no need for 99% of my
code to know these values after they have been set. I view the
criterion of a SELECT as being the values I actually use in my
application and the values of the key fields are
It's quite simple actually, there is absolutely no need for 99% of my
code to know these values after they have been set. I view the
criterion of a SELECT as being the values I actually use in my
application and the values of the key fields are only used inside the
query itself to specify which
Michael Bayer schrieb:
great news, that regex is gone in the trunk. try out the SVN trunk.
Thank you very much - trunk fixes my problems :-)
also yeah those column names are super wacky. :)
I'm happy already if they don't contain broken umlauts characters
or spaces :-)
fs
not entirely true... we need to know those values in sqlalchemy - we
couldn't issue lazy loads
Not true at all. Maybe in the current implementation, but it isn't
necessary whatsoever. Let's say you have class Thing, which is many to
one to class Owner. If you want to lazyload relation owner
not entirely true... we need to know those values in sqlalchemy - we
couldn't issue lazy loads
Not true at all. Maybe in the current implementation, but it isn't
necessary whatsoever. Let's say you have class Thing, which is many to
one to class Owner. If you want to lazyload relation owner
On Nov 14, 2007, at 11:44 AM, Chris M wrote:
not entirely true... we need to know those values in sqlalchemy - we
couldn't issue lazy loads
Not true at all. Maybe in the current implementation, but it isn't
necessary whatsoever. Let's say you have class Thing, which is many to
one to
Understandable - there is no reason to change how it works as long as
its possible to eagerload with deferred keys. Someone who is doing my
pattern of access isn't going to be lazyloading much anyway. Not
asking for any radical change, just discussing.
On Nov 14, 12:23 pm, Michael Bayer [EMAIL
Hi Marco,
There is a DB2 driver in the works, but I haven't heard much noise about it
lately, so I don't know what kind of progress is being made.
As for supported drivers, the three engines you mention are all supported, I
think that PG is probably has better test coverage than either Oracle or
Yep. That was it. Stupid me...
On Nov 13, 4:10 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Nov 13, 2007, at 8:25 AM, Koen Bok wrote:
Hi, I have this strange bug or problem...
I have a basic class like this mapped to a table with the same name.
Metatype is a relation to the metatype
Hi,
I can see that this has been discussed before, but I am totally
baffled as to what is happening.
I.
ubuntu
mysql version 5.0.38
with :
MySQL_python-1.2.2
SQLAlchemy-03.10
python-2.5
Using SA, I can insert and select unicode data with no problem. All
the mysql stuff looks like it is set to
david wrote:
Hi,
I can see that this has been discussed before, but I am totally
baffled as to what is happening.
I.
ubuntu
mysql version 5.0.38
with :
MySQL_python-1.2.2
SQLAlchemy-03.10
python-2.5
Using SA, I can insert and select unicode data with no problem. All
the mysql
17 matches
Mail list logo
