> will restore engine.echo today. what about Metadata's? why not leave some enginetype-indepedent kwargs there (or at least echo, its the most used in lets-try-this-now cases), which go together with the bind to the create()? i know i know explicit is better than implicit... noone would be forced to use them ;-) something like def __init__( ..., echo =None): ... me.echo = echo def create( ..., echo=None, **kargs4engine) if echo is None: echo me.echo .. create engine( bind, echo=echo, **kargs4engine)
? > leaving it out on session and pool, however (bet you didnt know > they had "echo" too...) i know but i always assumed all that is working (and it always has been so far) and its me/request going wrong, hence the sql echo... > On Aug 22, 2007, at 5:11 AM, svilen wrote: > > in 0.3, one could do > > meta = MetaData( whatever, echo=True) > > later, early 0.4, the echo kwarg was gone, so it got less > > convenient, adding another line: > > meta.bind.echo = True > > As of latest trunk, neither works, one has to explicitly do > > meta = MetaData( create_engine(whatever, echo=True)) > > which is probably fine for explicitness with lots of args, but is > > not very useful for a simple echo. > > > > IMO it is important to get the simplest use case (minimum > > explicit typing): > > meta = MetaData( dburl, echo=True) > > working. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
