Hi, Zardosht!
On Jan 15, Zardosht Kasheff wrote:
> Another question, are old timestamp fields stored the way is used to
> be? as a little endian integer? or are those now big-endian as well?
Yes, little endian.
(otherwise old tables wouldn't be readable in the new mariadb version)
Regards,
Serge
Another question, are old timestamp fields stored the way is used to be? as
a little endian integer? or are those now big-endian as well?
On Tue, Jan 15, 2013 at 2:32 PM, Sergei Golubchik wrote:
> Hi, Zardosht!
>
> On Jan 15, Zardosht Kasheff wrote:
> > Hello all,
> >
> > In MySQL/MariaDB 5.1,
Hi, Zardosht!
On Jan 15, Zardosht Kasheff wrote:
>
> Unfortunately, we need to do comparisons during phases when the Table
> object, and therefore the Field object, may not be around, such as
> during recovery. So for fixed length fields, we privately encode their
> length and metadata that expla
Thanks Sergei.
Unfortunately, we need to do comparisons during phases when the Table
object, and therefore the Field object, may not be around, such as during
recovery. So for fixed length fields, we privately encode their length and
metadata that explains how to compare them.
On Tue, Jan 15, 20
Hi, Zardosht!
On Jan 15, Zardosht Kasheff wrote:
> Hello all,
>
> In MySQL/MariaDB 5.1, when a timestamp field was used as a key, we
> used an integer compare to compare the fields. We assumed all integer
> fields (including date, time, and timestamp) could use an integer
> comparison to compare
Hello all,
In MySQL/MariaDB 5.1, when a timestamp field was used as a key, we used an
integer compare to compare the fields. We assumed all integer fields
(including date, time, and timestamp) could use an integer comparison to
compare the fields, and that they were either 1, 2, 3, 4 or 8 bytes lo
6 matches
Mail list logo
