Hi,
Just wanted to say thanks to those who helped me with this. Simon's solution
was exactly what I was looking for (though I have to admit I don't exactly
understand *how* it works!). But that's no longer an SQLAlchemy question...
Cheers,
Demitri
On Jul 8, 2010, at 5:49 AM, King Simon-NFHD78
thatsanicehatyouh...@mac.com wrote:
This is a bit tricky to explain. Imagine I have one database, and I create a
project (1) to work with that database (connections, table class definitions,
etc.). That is standalone (to me). I have another completely separate database
(2) on another host
-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of
thatsanicehatyouh...@mac.com
Sent: 07 July 2010 20:33
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] Using the declarative base across projects
Hi Lance,
Thanks
On Wed, 2010-07-07 at 11:13 -0400, thatsanicehatyouh...@mac.com wrote:
Hi,
I have a question that I can't find a satisfactory answer to. Apologies in
advance if it's more of a Python question, but it's possible that there is a
SA solution.
I have a project that defines a database
Hi Lance,
Thanks for your comments.
On Jul 7, 2010, at 12:28 PM, Lance Edgar wrote:
Why not just do this in project2 ?
import project.DatabaseConnection as db
Base = declarative_base(bind=db.engine)
# ... etc.
The DatabaseConnection class contains the particulars of the connection
