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 applica
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
to throw out
Flask-SqlAlchemy and see how it goes, but would like to find an easier way
first). Any suggestions are appreciated.
On Friday, May 16, 2014 5:02:57 PM UTC+10, gbr wrote:
True. I should have modified
def run_migrations_online():
Run migrations in 'online' mode
13, 2014, at 8:41 AM, gbr doub...@directbox.com javascript:
wrote:
In some Alembic upgrade scripts, I need to use application sessions to
make use of some code that requires these sessions. To avoid deadlocks from
blocking transactions I use the following lines to transparently call
Exactly what I was looking for - thanks.
On Sunday, March 30, 2014 10:43:12 AM UTC+11, Felix Schwarz wrote:
Am 29.03.2014 23:33, schrieb gbr:
There's one thing though that I haven't been able to work out yet (maybe
this
feature doesn't exist).
How about the stamp() command?
http
