Bug #67442
closedSetting NOT NULL on „BLOB“ column in Install Tool
100%
Description
To see this bug most patches under review for DBAL must be in the working tree, otherwise this will be swallowed by other bugs!
When the InstallTool suggests a change like this:
ALTER TABLE sys_category CHANGE l10n_diffsource l10n_diffsource longblob NOT NULL; Current value: longblob
this alteration will not be performed, it seems as if the NOT NULL is being silently swallowed, the statements logged by the DB server for this alteration are:
LOG: statement: ALTER TABLE "sys_category" ALTER COLUMN "l10n_diffsource" TYPE BYTEA LOG: statement: ALTER TABLE "sys_category" ALTER COLUMN "l10n_diffsource" SET DEFAULT ''
Manually setting the field to NOT NULL using a statement like this:
ALTER TABLE sys_category ALTER COLUMN l10n_diffsource SET NOT NULL; <pre> works and will be recognized by the install tool. Test Environment: TYPO3 7.3-dev@master + DBAL patches PostgreSQL 9.4.1
Updated by Morton Jonuschat over 9 years ago
Bug has been traced back to ADOdb which disables NOT NULL and DEFAULT globally for all DBMS types.
Pull request for ADOdb to make this behaviour configurable per DBMS: https://github.com/ADOdb/ADOdb/pull/118
Updated by Morton Jonuschat over 9 years ago
- Status changed from New to In Progress
Updated by Gerrit Code Review over 9 years ago
- Status changed from In Progress to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40398
Updated by Gerrit Code Review over 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40398
Updated by Morton Jonuschat over 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset d29068556c28e382039f6e8249a8af416fa5413e.