Fix reading/writing object of type mbr. An mbr consists of 4 flt values which were cast to int to be written and read as int and then cast to flt.  This means that values that don't fit in an int (decimals, out of range, flt_nil) were not read and written correctly.  This in turn meant that the WAL was useless for values of type mbr (which is where this is used). The old code (pre 2007) did it correctly, but not in a way that satisfied compilers. If a compiler starts complaining about the call to mnstr_readIntArray or mnstr_writeIntArray, use an int v[4] array and memcpy the values to and from this array before writing or after reading.
Fix reading/writing object of type mbr.
An mbr consists of 4 flt values which were cast to int to be written
and read as int and then cast to flt.  This means that values that
don't fit in an int (decimals, out of range, flt_nil) were not read
and written correctly.  This in turn meant that the WAL was useless
for values of type mbr (which is where this is used).
The old code (pre 2007) did it correctly, but not in a way that
satisfied compilers.
If a compiler starts complaining about the call to mnstr_readIntArray
or mnstr_writeIntArray, use an int v[4] array and memcpy the values to
and from this array before writing or after reading.

zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb