-
### Expected behavior
Upgrading the database schema from v2.6.0.a → v3.0.0.a with `optuna storage upgrade --storage `
### Environment
- Optuna version: 3.3.0
- Python version: 3.10.9
- OS: Window…
-
Here is the output I get:
```
$ pip3 install -r requirements.txt
Collecting alembic==1.8.0
Using cached alembic-1.8.0-py3-none-any.whl (209 kB)
...
Collecting typing-extensions
Using …
-
Scrolling through the issue as I was setting this up, I found the following that appear to be relevant. #43 #7 #20 and #39 .
Basically it comes down to the way that the triggers are added into the …
-
Bonjour à tous et meilleurs voeux !
Petit retour d'expérience d'une installation et migration de la bdd depuis un serveur Debian 10 avec Postgresql 11 vers un nouveau serveur Debian 12 avec Postgre…
-
**Migrated issue, originally created by Josh Kupershmidt ([schmiddy](https://github.com/schmiddy))**
I was a little surprised to see that the `alembic_version` table records only the current `version…
-
## CKAN version
2.11 fresh package install
## Describe the bug
crash adding initial sysadmin when "activity" plugin is loaded (default in package install).
It appears the db schema is missing a…
-
The documentation is unclear about native versioning's use of `temporary_transaction` table. Furthermore, should the `temporary_transaction` table be missing, even no warning is emitted.
I am using (…
ztane updated
8 years ago
-
At the moment, the "--help" is not very helpful.
## Actual behavior
```
(venv) user@pc project % flask db migrate revision --help
Usage: flask db migrate [OPTIONS] [ALEMBIC_ARGS]...
Wrap …
-
As title suggest, these seems to be a bug when creating trigger on a table that doesn't exist yet and is part of the same migration. In such case autogenerated create fails with error.
Example defi…
LKay updated
2 months ago
-
**Describe the bug**
After my nightly backup stopped and restarted the stacks, Riven no longer works. It appears the backend updated itself, and I am getting the below errors. I have also forced my…