TYPO3 Core

Do you really see a usecase for seconds?

I actually do :)

Imagine some radio broadcasting company that might want to store its scheduled broadcasts into database by TYPO3. They may want to past in the date and the time - even down to seconds - since they just have this data (or have some interface that includes part of the data automatically and shouldnt get lost).

uh - never have seen a start of broadcast at 21:03:13 :D

You may not see this data, but still it may be there... just imagine as an example some JavaScript (maybe AJAX) piece, that would be able to switch some content on a website almost in real-time sync with some broadcast via another media. That wouldn't be possible based on datetime, since you were lacking - the seconds.
And it wouldn't do any harm nor put a big overhead into the core to have datetimesec available as an option, would it?

However, if this one doesn't get any positive feedback within this thread, I won't submit it to the core list - since it admittedly might be considered as a case too special.

It just was so much easier and less overhead to patch TYPO3 for the almost available datetimesec by combining datetime and timesec than to implement a separate userfunc eg by using $TYPO3_CONF_VARS['SC_OPTIONS']['tce']['formevals'], that I couldn't resist.

So if you regarded this feature request as a poll for its usability - that would be appropriate, I suppose.

There has been an error in the initial version. Please use _v2