>>>>> "Oystein" == Oystein Grovlen <ystein> writes:
Oystein> Konstantin Osipov wrote:
>> * Øystein Grøvlen <Oystein.Grovlen@stripped> [09/05/22
>>> So far my Value object knows nothing about arithmetics, all they know
>>> about is how to convert between types. However, it needs to distinguish
>>> between more than just four types. For example, conversion between
>>> integer and string will be different for a Field_timestamp than for a
>> This just doesn't make sense to me. It's like saying that
>> conversion between an integer and a string will be different
>> depending whether this integer represents a datetime or, well, an
>> Isn't it easier to say (and code) that a conversion from an
>> integer to a string is not the same as conversion from a datetime to
>> a string? What am I missing?
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!
For information of MariaDB, the community developed server based on
source code from MySQL, check out www.askmonty.org