View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006982 | OXID eShop (all versions) | 4.01. Database handling | public | 2019-05-21 08:33 | 2022-02-02 09:39 |
| Reporter | mgmtp | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | 6.1.3 | ||||
| Summary | 0006982: Primary key for galera cluster | ||||
| Description | We try for our customer project to scale the database of an OXID enterprise shop (version 6.1.3) via a mariadb galera cluster. Galera requires a primary key in each table. But we have found some problems with different tables. These table have no primary key set: * oxadminlog * oxarticles2shop * oxattribute2shop * oxcategories2shop * oxdelivery2shop * oxdeliveryset2shop * oxdiscount2shop * oxinvitations * oxlinks2shop * oxmanufacturers2shop * oxnews2shop * oxselectlist2shop * oxvendor2shop * oxvoucherseries2shop * oxwrapping2shop Is a primary key planned foor these tables and will this be included in future releases? Are the following steps an option: * set the unique key of alle 2shop tables also as primary key * create a auto increment primary key for oxadminlog and oxinvitations Thanks for your help. | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | 7.1 | ||||
| Database Version | Not defined | ||||
| duplicate of | 0006981 | closed | Primärschlüssel bei Galera Skalierung |
