caosdb-mysqlbackend issueshttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues2023-10-23T11:32:53Zhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/49Create Tests for database migrations2023-10-23T11:32:53ZHenrik tom WördenCreate Tests for database migrationsThis is an essential step that is crucial for data preservation and should be (better) tested.
Should we keep a collection of old dumps for which we test the restore?This is an essential step that is crucial for data preservation and should be (better) tested.
Should we keep a collection of old dumps for which we test the restore?https://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/28Default installation target does not work for existing databases2022-07-22T08:41:32ZAlexander SchlemmerDefault installation target does not work for existing databasesFor a current setup I am working on, I am provided with an existing databases that will be used for the setup of caosdb.
I set up the options in `.config`, but during running `make install` I get:
```
A database with with the name '......For a current setup I am working on, I am provided with an existing databases that will be used for the setup of caosdb.
I set up the options in `.config`, but during running `make install` I get:
```
A database with with the name '...' exists already.
Call 'make drop-...' to delete that database or change the database
name in your .config file
./utils/make_db grant
Granting admin privileges to '...'@'localhost'
ERROR 1227 (42000) at line 1: Access denied; you need (at least one of) the CREATE USER privilege(s) for this operation
make: *** [Makefile:44: _grant] Error 1
```
Is there an automated way to set up the existing database for this use case?
## DoD ##
- [ ] There is a configuration option in the mysqlbackend config, that allows an installation in an existing database.
## Known problems ##
- SUPER privileges on the existing database are required to be able to create functions and procedures.Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/8Docker: proper check for database completeness2022-07-22T10:00:29ZHenrik tom WördenDocker: proper check for database completeness*Created by: Timm Fitschen*
If the database is already at the current stage, no patch scripts should be called at all.
- [ ] Only call those patch scripts whose version is above the current database version.
**Imported comments:**
...*Created by: Timm Fitschen*
If the database is already at the current stage, no patch scripts should be called at all.
- [ ] Only call those patch scripts whose version is above the current database version.
**Imported comments:**
*By Quazgar on 2020-01-08T15:07:13.036Z*
changed the description
*By Timm Fitschen on 2019-10-01T09:02:48.536Z*
Moved from internal Gitlab: https://gitlab.indiscale.com/caosdb/internal/docs/issues/51
*By Timm Fitschen on 2019-10-01T09:02:10.929Z*
changed due date to October 07, 2019Daniel HornungDaniel Hornunghttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/17Refactor reference query procedures for LIKE operator2021-07-14T12:07:09ZHenrik tom WördenRefactor reference query procedures for LIKE operator*Created by: Timm Fitschen*
Currently, the operator (`=` or `LIKE`) is guessed by the stored procedure. Make it explicit, the server already knows which operator is the right one.
Procedures:
* [ ] `initPOVRefidsTable`
* [ ] `initBack...*Created by: Timm Fitschen*
Currently, the operator (`=` or `LIKE`) is guessed by the stored procedure. Make it explicit, the server already knows which operator is the right one.
Procedures:
* [ ] `initPOVRefidsTable`
* [ ] `initBackReference`
* [ ] `initSubEntity`Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/19Due to special handling of descriptions, `FIND ENTITY WITH description = ......2021-07-14T12:09:47ZHenrik tom WördenDue to special handling of descriptions, `FIND ENTITY WITH description = ...` doesn't work.*Created by: Timm Fitschen*
Currently, descriptions are stored inside the entities table which is not being considered by the `applyPOV` procedure.
# DoD
* [ ] Refactor `entities` table and move descriptions to `text_data`.
## Option...*Created by: Timm Fitschen*
Currently, descriptions are stored inside the entities table which is not being considered by the `applyPOV` procedure.
# DoD
* [ ] Refactor `entities` table and move descriptions to `text_data`.
## Optional
* [ ] Remove `desc_overrides` table and store description overrides in `text_data`.
**Imported comments:**
*By Timm Fitschen on 2020-06-16T10:00:00.307Z*
mentioned in merge request !13
*By Timm Fitschen on 2020-06-16T09:58:12.403Z*
changed the description
*By Timm Fitschen on 2020-06-16T09:57:43.749Z*
marked this issue as related to #20
*By Timm Fitschen on 2020-06-16T09:57:33.139Z*
changed the description
*By Timm Fitschen on 2020-06-16T09:57:14.985Z*
mentioned in issue #20Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/20Remove `name_overrides` table2021-07-14T12:10:20ZHenrik tom WördenRemove `name_overrides` table*Created by: Timm Fitschen*
With names being stored inside of the `name_data` table since !13, the `name_overrides` table is no longer needed.
# DoD
* [ ] remove the `name_overrides` table and refactor the insertion of properties such...*Created by: Timm Fitschen*
With names being stored inside of the `name_data` table since !13, the `name_overrides` table is no longer needed.
# DoD
* [ ] remove the `name_overrides` table and refactor the insertion of properties such that overrides are stored inside the `name_data` table.
**Imported comments:**
*By Timm Fitschen on 2020-06-16T10:00:00.262Z*
mentioned in merge request !13
*By Timm Fitschen on 2020-06-16T09:58:47.716Z*
changed the description
*By Timm Fitschen on 2020-06-16T09:57:43.781Z*
marked this issue as related to #19
*By Timm Fitschen on 2020-06-16T09:57:33.236Z*
mentioned in issue #19Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.com