Project

General

Profile

Actions
Copy link

Bug #82128

closed

Database migration/analyzer fail on VARCHAR default NULL

Added by Jakob Berlin over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-08-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

In install tool after running "Database analyzer" I get proposed queries like:

ALTER TABLE tablename CHANGE field zzz_deleted_field varchar(255) NOT NULL default NULL;

This is not working as a Not-Null-Field could not setup as default null obviously.

Is this a problem of the created field which was tx_sffeuser_corpcountry here or could it (maybe never the less) handled by SqlSchemaMigrationService to avoid such queries?

Actions
Copy link
 #1

Updated by Jakob Berlin over 7 years ago

Obvious workaround if someone run into this:

Run the query on the database directly but modified e.g. to:

ALTER TABLE tablename CHANGE field zzz_deleted_field varchar(255) default NULL;

Actions
Copy link
 #2

Updated by Wouter Wolters over 7 years ago

  • Status changed from New to Needs Feedback

Is this a problem on version 8.7?

Actions
Copy link
 #3

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Needs Feedback to Closed

No feedback since the last 90 days => closing this issue.

Moreover, the whole codebase has changed in this regard (TYPO3 8.7.x uses Doctrine) and we won't change this anymore for version 7.

If you think that this is the wrong decision, please reopen it or open a new issue with a reference to this one. Thank you.

Actions
Copy link

Also available in: Atom PDF