[TYPO3-core] Strategy for deprecation log

Markus Klein klein.t3 at mfc-linz.at
Mon Apr 1 15:57:30 CEST 2013


> 2) optionally checks for duplicates using the sys_registry
>> > IMHO a NO GO. Please don't use any database stuff in deprecation handling.


1.) Because I don't think it's a good idea to mix concepts of different "abstraction levels". Database access and handling is a far higher concept than the rather lowlevel deprecation handling. This shouldn't be mixed.
It MIGHT lead to serious troubles in the (unknown) future, especially when it comes to database functions being deprecated. Somewhat a chicken - egg problem.

2.) Accessing the DB is probably even slower than reading the small plain file.

Kind regards

More information about the TYPO3-team-core mailing list