[TYPO3-dev] ADOdb extended dates prototype

[David Bruehlmeier]

Hi,

> But my idea would be not to "misuse" the current "date" and "datetime"
> eval fields, because that would mean rewriting every extension that
> expects that fields to hold UNSIGNED INTs. I would rather add a new
> "adodate" or "bigdate" and "bigdatetime" eval fields that handle that
> new situation. This way we guarantee backwards compatibility, we have
> two new eval field types which internally use adodb and maybe some fancy
> JS for client-side calculation (maybe regular new Date() from JavaScript
> already handle signed bigint's???). New extensions can make use of those
> fields, old extensions still work, but upgrades might change to the new
> fields. Old eval types are marked as "deprecated" now and nobody is
> encouraged to use them.

+1

Yes, this should become a new field type. The current date/time field 
types might be marked deprecated to achieve a smooth transition.

Regards
Dave