Task #13973
Possible table name clash with Doctrine
Status: | Resolved | Start date: | 2011-03-22 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
Category: | Persistence | |||
Target version: | TYPO3 Flow Base Distribution - 1.0 beta 1 | |||
Sprint: | Has patch: | |||
PHP Version: | Complexity: |
Description
When having two entities with the same unqualified classname, they both end up with the same table name by default (ie. Blog\Domain\Model\Post vs. Forum\Domain\Model\Post).
Associated revisions
[!!!][TASK] Change generated table structure for Doctrine
This makes all column names lowercase and creates table names with a
lower risk of name clashes.
Resolves: #13973
Change-Id: I10316deddb045e0d0f1d078d44d3aca5df0bc68a
History
#1 Updated by Karsten Dambekalns over 4 years ago
- Status changed from Accepted to Needs Feedback
What we need to discuss is how to build a prefix to avoid those clashes, keeping in mind the table name length limits some high-end databases impose.
#2 Updated by Karsten Dambekalns over 4 years ago
- Status changed from Needs Feedback to Under Review
#3 Updated by Karsten Dambekalns over 4 years ago
- Target version set to 1.0 beta 1
#4 Updated by Mr. Hudson over 4 years ago
Patch set 2 of change I10316deddb045e0d0f1d078d44d3aca5df0bc68a has been pushed to the review server.
It is available at http://review.typo3.org/1690
#5 Updated by Mr. Hudson over 4 years ago
Patch set 3 of change I10316deddb045e0d0f1d078d44d3aca5df0bc68a has been pushed to the review server.
It is available at http://review.typo3.org/1690
#6 Updated by Mr. Hudson over 4 years ago
Patch set 4 of change I10316deddb045e0d0f1d078d44d3aca5df0bc68a has been pushed to the review server.
It is available at http://review.typo3.org/1690
#7 Updated by Karsten Dambekalns over 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 767e33563fab315de25172634e7161e52978bfea.