Re: stack trace with key error from: alembic revision --autogenerate -m "first rev"

2015-04-20 Thread Dewey Gaedcke
ssed into the event-handler. I'm assuming it's via the metadata key but having no luck finding it there. Thanks, Dewey On Tuesday, December 23, 2014 at 5:07:34 PM UTC-6, Dewey Gaedcke wrote: > > Is it likely that this construct: > > @event.listens_for(Column, "

Re: stack trace with key error from: alembic revision --autogenerate -m "first rev"

2014-12-23 Thread Dewey Gaedcke
that but I don't really understand the suggestion. Thanks, Dewey On Tuesday, December 23, 2014 5:56:03 PM UTC-6, Michael Bayer wrote: > > > > Michael Bayer > wrote: > > > Dewey Gaedcke > wrote: > > > > this is the table that’s being reflected

stack trace with key error from: alembic revision --autogenerate -m "first rev"

2014-12-23 Thread Dewey Gaedcke
Is it likely that this construct: @event.listens_for(Column, "before_parent_attach") def attach(target, cls): # cls is the table obj, not the declarative class target.name = "%s%s" % (cls.name[0:4], target.name) is interfering with Alembic?? I'm getting this stack trace and it changes i