Bug #79282
closed
SQL identities and IDENTITY_INSERT with doctrine on mssql server
0%
Description
On mssql servers dumps/importing with preset ids will fail as IDENTITY_INSERT is not set/allowed by default.
E.g. #79143
If we want IDENTITY_INSERT we would need to write some custom integration to set it on the just the table be inserted into at the current moment as it can only be ON for one table at a time.
In general it is probably wiser to not rely on inserting ids or altogether move away from sql dumps for static data shipped by extensions/distributions.
Updated by Christian Kuhn over 7 years ago
I guess solution depends on actual use case ... i'm currently compiling some patches for mssql to get more functional tests green with mssql: for the functional tests, they pretty heavily rely on setting IDENTITY, this can't be easily avoided. Thus, for the functional "import data sets" part, I now added identity_insert on for now.
for WIP patch, see: https://review.typo3.org/#/c/52912/
Updated by Morton Jonuschat over 7 years ago
- Status changed from New to Resolved
MSSQL is in experimental support, we are currently running functional tests against it. This should have been resolved with the integration work done for that.
Updated by Gerrit Code Review over 7 years ago
- Status changed from Resolved 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 https://review.typo3.org/53352
Updated by Anja Leichsenring over 6 years ago
- Status changed from Under Review to New
Updated by Anja Leichsenring over 6 years ago
can someone please check whether this issue still exists? There had been some action in the MSSQL area lately.
Updated by Sebastian Hofer almost 6 years ago
Yes, this issue does still exist. We currently have to deal with a MSSQL server and have problems with this. We would have to set IDENTITY_INSERT to ON for certain tables during writing, but it seems, that this is not possible.
Updated by Susanne Moog over 4 years ago
- Status changed from New to Closed
The issue itself may still exist, however this is more a general topic than a concrete issue. If you are using SQLServer with TYPO3 and have problems like this, please report single bug reports with steps to reproduce for each problem.
I had a TYPO3 installation based on MSSQL running and the core functionality was working quite well, that's why I ask to report separate issues if there are still problems.
In a broader scope, I agree with Johannes that inserting ID values and sql dumps are a less than ideal solution, however that would need a separate project to rework.