I did just that this afternoon to link across heterogeneous
dataservers. Modulo the inevitable awkwardness from having two
different names for the same thing (i.e. Asset and EjvAsset), this was
very easy:
class_mapper(Asset).add_properties({
'EjvAsset' : relation(EjvAsset,
that error is just a table already exists. pass checkfirst=True to
your table.create() call.
On Apr 16, 2009, at 6:21 AM, JanW wrote:
Hi all,
I've playing around with SQLAlchemy for a few months, being very happy
with the results.
As my adventures are getting gradually more complex I
Oops, yes of course.
Sorry, I copied the error message from the wrong terminal.
The relevant error message would be this one:
Traceback (most recent call last):
File demo.py, line 51, in module
result = Person.query().all()
File /Library/Frameworks/Python.framework/Versions/2.5/lib/
if the issue is, youre doing a JOIN across two tables that are in
different databases, that's not going to work. you cant issue a JOIN
across two different databases unless both of those tables are
accessible using schemas or remote database links within the same
process.
On Apr 16,
OK, thanks, so does that mean that mapping one class against multiple
tables in different databases is something very exotic and probably
bad practice?
Or is there some elegant way to achieve this?
Thanks,
Jan.
On Apr 16, 4:42 pm, Michael Bayer mike...@zzzcomputing.com wrote:
if the issue is,
On Apr 16, 2009, at 10:50 AM, JanW wrote:
OK, thanks, so does that mean that mapping one class against multiple
tables in different databases is something very exotic and probably
bad practice?
its an impossible practice unless you're using DBLINK...
Or is there some elegant way to
