Re: suspected bug in script.get_base()

Hello, Thanks for fixing the bug. Regards, Godfryd On Fri, Dec 27, 2013 at 4:26 PM, Michael Bayer wrote: > Note we’re up to 0.6.1 right now, but still looks like that’s just an API > method that isn’t used or tested anywhere, so yup. Fixed in > rc0fbd149c4dc58488967eb2828a. > > > > On Dec 27,

alembic 0.6.2 released

hey list - Pushed out Alembic 0.6.2. The big deal in this one is more changes/rework of the new index/unique constraint autogenerate feature. Turns out that MySQL has all kinds of left turns as well, not just Postgresql, creating indexes and unique constraints implicitly for each other and

Re: suspected bug in script.get_base()

Note we’re up to 0.6.1 right now, but still looks like that’s just an API method that isn’t used or tested anywhere, so yup. Fixed in rc0fbd149c4dc58488967eb2828a. On Dec 27, 2013, at 9:30 AM, Michal Nowikowski wrote: > Hello, > > I'm using Alembic 0.4.1. > I experience such exception: > /

suspected bug in script.get_base()

Hello, I'm using Alembic 0.4.1. I experience such exception: /usr/lib/python2.7/dist-packages/alembic/script.pyc in get_base(self) 283 """ 284 for script in self._revision_map.values(): --> 285 if script.down_revision is None \ 286 and script