Michael Widenius wrote:
>>>>>> "Oystein" == Oystein Grovlen <ystein> writes:
> Oystein> That's really what I tried to say. Both integer and datetime will
> Oystein> internally be represented by a longlong, but the conversion from
> Oystein> longlong to string will be different.
> Plese don't do that!
> We want to add microsecond support to datetime and having datetime as
> longlong would make this quite hard to do!
I agree, but datetime is converted to longlong today so I am not
changing anything here. The idea is to fix this in two steps. First,
type conversion code (e.g., from datetime to longlong) that is
duplicated in many item/field classes is moved to a single place (the
Value object). Then, it should become much easier to introduce new type
representations (e.g., a special date/time representation).