Bug #81784
closed
DatabaseConnection function INSERTmultipleRows does not allow NULL values
0%
Description
Just like issue #53662 which affected INSERTquery:
the INSERTmultipleRows() method in the DatabaseConnection class does not supply the $allowNull parameter to the fullQuoteArray() method.
This causes values that should be NULL to be inserted as empty strings '' instead.
Visible frontend effects will for instance happen with sys_file_reference (title = NULL means no element specific value so load title from sys_file_metadata; title = '' means empty string as specific value - result in a filelinks element would be showing filename instead of metadata title...)
Updated by Christian Reiter almost 7 years ago
- Related to Bug #53662: DatabaseConnection INSERTquery does not allow NULL values added
Updated by Christian Kuhn over 5 years ago
- Status changed from New to Closed
Hey. Thanks for reporting this issue. The core switched to doctrine with version 8, so it should not be a problem with that version anymore. You should use that new API since v8 anyway. The class has even been removed from core (extracted as optional external extension for b/w compat) in v9. v7 is now in 'hard blockers only' mode, so we will not fix it there anymore, either.
If you really rely on this, you probably will have to patch an instance yourself.
I'll close this issue for now.