http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-06-12T10:24:01ZTYPO3 ForgeTYPO3 Core - Feature #84639: Defining a FOREIGN KEY constraint on a 1:n relation ends in an SQL failure when editing rows in these tables via backend or extbasehttp://forge.typo3.org/issues/84639?journal_id=3669012018-06-12T10:24:01ZBenni Mackbenni@typo3.org
<ul><li><strong>Target version</strong> changed from <i>8.7.13</i> to <i>8.7.19</i></li></ul> TYPO3 Core - Feature #84639: Defining a FOREIGN KEY constraint on a 1:n relation ends in an SQL failure when editing rows in these tables via backend or extbasehttp://forge.typo3.org/issues/84639?journal_id=3727742018-09-06T14:54:59ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Target version</strong> changed from <i>8.7.19</i> to <i>Candidate for patchlevel</i></li></ul> TYPO3 Core - Feature #84639: Defining a FOREIGN KEY constraint on a 1:n relation ends in an SQL failure when editing rows in these tables via backend or extbasehttp://forge.typo3.org/issues/84639?journal_id=3737302018-09-19T00:53:43ZTymoteusz Motylewskit.motylewski@gmail.com
<ul></ul><p>Thanks for the report @Stefan.<br />Can you please provide a minimal code allowing to reproduce the issue with vanilla core?<br />e.g. please attach a test extension and steps to reproduce.<br />Thanks</p> TYPO3 Core - Feature #84639: Defining a FOREIGN KEY constraint on a 1:n relation ends in an SQL failure when editing rows in these tables via backend or extbasehttp://forge.typo3.org/issues/84639?journal_id=3884622018-10-05T15:04:33ZStefan P
<ul></ul><p>Sorry, don't have time for this. Just put an index on any simple 1:n (IRRE) relation to test it.</p> TYPO3 Core - Feature #84639: Defining a FOREIGN KEY constraint on a 1:n relation ends in an SQL failure when editing rows in these tables via backend or extbasehttp://forge.typo3.org/issues/84639?journal_id=4206342020-03-26T08:22:06ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li><li><strong>Category</strong> set to <i>DataHandler aka TCEmain</i></li></ul> TYPO3 Core - Feature #84639: Defining a FOREIGN KEY constraint on a 1:n relation ends in an SQL failure when editing rows in these tables via backend or extbasehttp://forge.typo3.org/issues/84639?journal_id=4584432021-11-26T01:28:42ZChristian Kuhnlolli@schwarzbu.ch
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Hey.</p>
<p>I'm going to close the issue for now: The core has no support for foreign key constraints whatsoever in its current state. Adding this probably requires quite a bit of work, a lot of dedicated time and many patches. It might become feasible when the DataHandler is refactored and simplified enough to give an overview on what needs to be done.</p>
<p>This issue here won't help much for now in this regard. In case we pick this up again, we'll created new tickets that include dedicated tasks.</p>
<p>I hope that's fine with everyone for now.</p>