Say I have a customized legacy datatype, based on ezstring.
For quick usage in ez5, I can register it to use the ezstring fieldtype and storage adapter.

But when a TextLine/Type object is created, it always says "ezstring" in its getFieldTypeIdentifier() call, which would not be 100% correct in this case.

It would be nice if all existing fieldtypes which have no constructor, would behave more like the eznull fieldtype does: have a constructor which takes the identifier, allowing user to inject it if they need