Repository navigation
Fix fatal PRIMARY KEY (Array) on fresh install from array primary key - #92
Merged
Merged
Conversation
TheWitness
requested review from
bmfmancini and
xmacan
and
a balanced review from Copilot
October 15, 2026 13:26
There was a problem hiding this comment.
🟢 Approval recommended
The focused fix covers all creation paths, preserves existing-table updates, and has no unresolved findings.
0 open findings
What changed in this PR
Fixes table creation failures by adapting primary-key definitions to Cacti’s create API while preserving the array format required for schema updates.
Changes:
- Converts array primary keys to scalar strings on all table-creation paths.
- Adds regression coverage for scalar creation keys and unchanged canonical definitions.
| File | Description |
|---|---|
| tests/Unit/GexportSetupTableTest.php | Tests primary-key formats for creation and canonical definitions. |
| includes/database.php | Adds the conversion helper and applies it to install and upgrade creation paths. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
xmacan
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
On a fresh install (and whenever the upgrade path creates a missing table), gexport hands
api_plugin_db_table_create()a table definition whoseprimaryis declared in the array form:Down to this plugin''s
compat = 1.2.29floor,api_plugin_db_table_create()(lib/plugins.php) interpolates the primary key straight into the DDL string:With an array, PHP renders it as
PRIMARY KEY (`Array`), so theCREATE TABLEfails and the table is never created on Cacti 1.2.29-1.2.31.This is the fresh-install mirror of the upgrade-path fatal fixed in plugin_routerconfigs #191:
api_plugin_db_table_create()requires the scalar primary form, whiledb_update_table()requires the array form.Fix
Add a
gexport_create_definition()helper that flattens an arrayprimaryto the backtick-joined scalar form, and wrap everyapi_plugin_db_table_create()call with it. The canonical*_table_data()definitions keep the array form thatdb_update_table()still requires on the upgrade path, so both paths get the form they need. This mirrors the helpers already present in plugin_maint, plugin_apcupsd, plugin_exlist, plugin_lsflog and plugin_stream.Validation
php -l includes/database.php- no syntax errors.