[postgis-users] Proposed SQL interface for PGRaster

[Markus Schaber]

Hi, Marc-Cave,

Mark Cave-Ayland wrote:

> Thanks for an interesting proposal. My only comment so far would concern
> the endian-ness of the raster data if it is stored as binary - for
> example, what would happen in the case of dumping a PostgreSQL database
> containing pgrasters on an Intel machine and restoring it on a Power
> machine with respect to the int16/32/64 and float32/float64 types?
> Perhaps you need to store the endian-ness of the data as it is inserted
> into the database, and then perform optional on-the-fly conversion
> depending upon the current processor?

I think it's better to always store in the current machine endianness,
for performance reasons.

Only the binary input/output functions need to either specify the
endianness via a flag, or always use network byte order.

Thanks,
Markus


-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org