I've looked in the source sqlalchemy/engine/base.py under the class
ExecutionContext and it does not contain this method postfetch_cols()
as documented. I've checked in 0.7.7, 0.6.9 stable versions as well as
0.8 am I being silly and missing something?
Details here:
I'm confused at how to use *orm.aliased()*. I'm using declarative base.
I have a class defined from
Base.metadata.reflect(engine)
class Summary(Base):
__table__ = Base.metadata.tables['summary']
Now, I want to use that class in a self join
class JoinSummary(Base):
s1 =
On Thursday, June 7, 2012 12:54:51 PM UTC-4, Ben Hitz wrote:
My first tests with Autoload=true had me scrambling to look at the .sql
file or the DB itself to remember what the heck the columns were called.
(So if you paying close attention, I think I just switched the question
from can
postfetch_cols() only applies to INSERT and UPDATE statements where defaults
might have been fired off. Currently the execution context doesn't take the
step of placing a blank collection (or raising an error) in the case of
statements where this collection does not apply.
On Jun 8, 2012, at
I know that kinterbasdb does not support python3, but there is an alternative
driver fdb which does. This is the driver recommended by the firebird project.
http://pypi.python.org/pypi/fdb/
I copied the kinterbasdb driver in sqlalchemy to a new file fdb.py and made
some minimal changes,
On Friday, June 8, 2012 8:56:45 AM UTC-4, Michael Bayer wrote:
How come you're making some kind of mapping to this new __select__, but
then when you use query() you're not making this query towards the
JoinSummary class ? the example seems a little torn as to what it wants to
do.
Sorry,
Thank you, good sir.
I was not using metadata.reflect()... but because I had defined/imported a
class manually, that table and related tables were populated in
metadata.tables().
.reflect() gets everything I would expect.
Of course, I have already wasted 20 minutes entering the 7 tables by
