caosdb-mysqlbackend issueshttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues2024-03-04T08:35:38Zhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/50Release Process: release-branch in Server uses dev in mysql?2024-03-04T08:35:38ZHenrik tom WördenRelease Process: release-branch in Server uses dev in mysql?## Summary
*Please give a short summary of what the issue is.*
## Expected Behavior
*What did you expect how the software should behave?*
## Actual Behavior
*What did the software actually do?*
## Steps to Reproduce the Problem
*P...## Summary
*Please give a short summary of what the issue is.*
## Expected Behavior
*What did you expect how the software should behave?*
## Actual Behavior
*What did the software actually do?*
## Steps to Reproduce the Problem
*Please describe, step by step, how others can reproduce the problem. Please try these steps for yourself on a clean system.*
1.
2.
3.
## Specifications
- Version: *Which version of this software?*
- Platform: *Which operating system, which other relevant software versions?*
## Possible fixes
*Do you have ideas how the issue can be resolved?*Henrik tom WördenHenrik tom Wördenhttps://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/47Investigate how passwords table survived.2023-10-18T07:49:24ZHenrik tom WördenInvestigate how passwords table survived.see #46
It should have been deleted long ago.
what about `procedures/insertUser.sql:INSERT INTO passwords VALUES (@LAST_UserID, Password);
`see #46
It should have been deleted long ago.
what about `procedures/insertUser.sql:INSERT INTO passwords VALUES (@LAST_UserID, Password);
`https://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/42Are mysql and mariadb getting inkompatible?2023-09-25T11:01:24ZHenrik tom WördenAre mysql and mariadb getting inkompatible?## Summary
> /usr/bin/mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
How shall we deal with this## Summary
> /usr/bin/mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
How shall we deal with thisTimm Fitschent.fitschen@indiscale.comHenrik tom WördenTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/40Plan: Next steps for implementing performance improvements2024-03-04T08:35:35ZFlorian SpreckelsenPlan: Next steps for implementing performance improvementsAus Planungsissue https://gitlab.indiscale.com/caosdb/internal/all/-/issues/1501:
## Allgemeine Performanceverbesserungen
Machen wir auf eigene Kosten. @henrik plant, wie das in kleinere Häppchen zerlegt werden kann, inkl. SQL Unit Tes...Aus Planungsissue https://gitlab.indiscale.com/caosdb/internal/all/-/issues/1501:
## Allgemeine Performanceverbesserungen
Machen wir auf eigene Kosten. @henrik plant, wie das in kleinere Häppchen zerlegt werden kann, inkl. SQL Unit Tests, dann entsprechende Issues in die nächsten Sprintplanungen mit aufnehmen.
## DoD
- [ ] Es gibt Issues für die Implementierung (auch von SQL-Unittests+Pipeline), die klein genug sind, dass sie in den nächsten wenigen Sprints angegangen werden können.Henrik tom WördenHenrik tom Wördenhttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/39Store integral data as BIGINT.2024-03-03T21:10:45ZDaniel HornungStore integral data as BIGINT.## Summary
Integral numeric data should be stored as LONG, because sometimes people already start querying for numbers which are too large for 32 bit integers.
## Possible fixes
* (Change the datatype of the `integer_data` table to B...## Summary
Integral numeric data should be stored as LONG, because sometimes people already start querying for numbers which are too large for 32 bit integers.
## Possible fixes
* (Change the datatype of the `integer_data` table to BIGINT.)
* Make sure that the server also sends and can receive BIGINTs.
* Make sure that all APIs and client libraries support 64 bit integers. (Queries excluded)Daniel HornungDaniel Hornunghttps://gitlab.indiscale.com/caosdb/src/caosdb-mysqlbackend/-/issues/38Error importing SQL dump into a recent mariadb database2022-07-22T09:24:35ZAlexander SchlemmerError importing SQL dump into a recent mariadb databaseIs it possible to just import an SQL dump (created by linkahead backup) into a normal maria db database (without further preparations)? I want to inspect the contents of some tables.
I tried (after having created database `caosdb_bmpg`)...Is it possible to just import an SQL dump (created by linkahead backup) into a normal maria db database (without further preparations)? I want to inspect the contents of some tables.
I tried (after having created database `caosdb_bmpg`):
`mysql -u root caosdb_bmpg < dump-filename.sql`
The import (of the tables I needed) seems to be there, but there was an error leading to an interruption of the sql script just before the end:
```
ERROR 1064 (42000) at line 1954: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'Offset INT UNSIGNED) RETURNS varbinary(255)
READS SQL DATA
BEGIN
...' at line 2
```
Maria DB version: 10.6.5-2 (on archlinux)Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://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