Indeed, I was using version 1.0.9 and didn't realise that this wasn't an
issue with alembic. Thanks for the quick response.
On Friday, 28 June 2019 22:30:49 UTC+2, Mike Bayer wrote:
>
>
>
> On Fri, Jun 28, 2019, at 4:01 PM, gbr wrote:
>
> I've upgraded my application to Python 3.7 and to the
On Fri, Jun 28, 2019, at 4:01 PM, gbr wrote:
> I've upgraded my application to Python 3.7 and to the latest version of
> Alembic which triggers an exception when `context.get_current_revision()` is
> called.
>
> ```
> File "app.py", line 395, in check_database_version
> current_rev =
I've upgraded my application to Python 3.7 and to the latest version of
Alembic which triggers an exception when `context.get_current_revision()`
is called.
```
File "app.py", line 395, in check_database_version
current_rev = context.get_current_revision()
File
Thanks so much for the detailed answer Mike, and for the quick fix! You're
the best.
On Thu, Jun 27, 2019 at 7:13 PM Mike Bayer wrote:
>
>
> On Thu, Jun 27, 2019, at 12:02 PM, Charles-Axel Dein wrote:
>
> Hi,
>
> I'm trying to have a deleted_at column on my records. I use MySQL and
> latest
