Changes between Version 2 and Version 3 of Ticket #50244, comment 10
- Timestamp:
- 06/10/2020 02:08:33 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #50244, comment 10
v2 v3 11 11 > In pre validation mode, validation will happen twice. Once when we check every request for passing validation, and then again in the individual dispatch. Adjusting this to only happen once makes me nervous, but there would be a performance benefit to it only happening once. 12 12 13 The only thing that could go wrong there is something unexpected happening between the batch validation and the handler invocation, e.g. requesting a batch of two requests, both trying to insert a row with the same value that's subject to an UNIQUE constraint - I think core should protect developers from doing that, but offer an option to opt out of this protection when more performance is required. Maybe splitting pre-validation into two modes like `validation=pre` and `validation=pre-only`?13 The only thing that could go wrong there is something unexpected happening between the batch validation and the handler invocation, e.g. requesting a batch of two requests, both trying to insert a row with the same value that's subject to an UNIQUE constraint - I think core should protect developers from doing that, but offer an option to opt out of this protection when more performance is required. Maybe by splitting pre-validation into two modes like `validation=pre` and `validation=pre-only`? 14 14 15 15 > I've omitted support for GET requests entirely at the moment.