Database needs to be upgraded to version 1.5.r38, it seems you are using phpipam version 1.5.r37! #3443
Labels
Comments
|
Hi, Can you provide your MySQL/MariaDB version and the output of the SQL command To progress you can apply the update queries shown on the upgrade page manually and skip this one. |
|
Hello, |
|
Currently operating on Azure MYSQL PaaS DB V5.7. Seen fix and will give it a try, thanks. |
4o66
added a commit
to 4o66/phpipam
that referenced
this issue
Nov 22, 2021
* 1.5: pull upstream 1.5 Feature: Warn when php and db schema versions do not match Update php-saml (3.6.1) and xmlseclibs (3.1.1) submodules SAML JIT Provisioning (phpipam#3389) Bugfix: Fix remaining version-check comparisons. Bugfix: Fix 'New version available' widget Bugfix: 1.5.38 Upgrade SQL syntax error (<=MySQL 5.7) Bugfix: 1.5.38 Upgrade SQL syntax error (<=MySQL 5.7). Fixes phpipam#3443 Feature: dbschema 38 Refactor: Cleanup upgrade_queries Bugfix: Database stored sessions require the php_sessions table to exist (dbversion>=3) Update changelog. Fix escape_input() Bugfix: SAML return to same page when session expires.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Issue relating to the execution to automated DB upgrade incorrect syntax.
phpIPAM version
Bug fixes are supported in the latest production and development releases. Please update to a supported release before reporting issues. Please search for existing Issues (including closed Issues) before submitting duplicates.
Versions of phpIPAM known to contain the issue (delete as appropriate).
version 1.5.r37 to 1.5.r38
Your Environment (please supply the following information):
Steps To Reproduce
Please include steps to reproduce the issue:
Automated upgrade prompt as follows:
SQLSTATE[42000]: Syntax error or access violation: 1101 BLOB, TEXT, GEOMETRY or JSON column 'command' can't have a default value
Failed query:
ALTER TABLE
logsCHANGEcommandcommandtext DEFAULT '0';The text was updated successfully, but these errors were encountered: