Project

General

Profile

Actions

Bug #23465

closed

db compare in install tool and ext-manager reports no-op changes e.g. for int columns

Added by Björn Pedersen about 14 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2010-08-27
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Just one example line from the install tool:

ALTER TABLE tx_frm2_conferences_Attendee CHANGE tstamp tstamp INT UNSIGNED default 0;
Current value: int(10) unsigned default '0'

mysql-server-5.1.42

The comparison for default values should strip the quotes for int-columns.

(issue imported from #M15577)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #16276: Database Analyser - Compare proposes "ALTER ..... NOT NULL" again and againClosed2006-06-23

Actions
Related to TYPO3 Core - Bug #19029: Database Analyser: "Compare with $TCA" displays errorsClosed2008-06-27

Actions
Actions #1

Updated by Ernesto Baschny almost 14 years ago

This probably won't be changed in 4.5.0 final (lack of time / manpower), but since it affects all released versions, a fix might come in at a later point. Thanks for your contribution!

Actions #2

Updated by Björn Pedersen almost 14 years ago

Yes, it is not an urgent change at all.

Actions #3

Updated by Björn Pedersen almost 13 years ago

  • Target version deleted (0)

Related to http://forge.typo3.org/issues/15772, see also the discussion in typo3.dev 'Database compare and database modification inconsistencies'.

Actions #4

Updated by Alexander Opitz almost 10 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?

Actions #5

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

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

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF