Opened 5 years ago

Last modified 4 months ago

#2263 new task

[raster] Audit usage of serialize/deserialize vs wkb/hexwkb

Reported by: dustymugs Owned by: dustymugs
Priority: high Milestone: PostGIS Fund Me
Component: raster Version: trunk
Keywords: Cc:

Description

An audit needs to be done to delineate the usage of serialize/deserialize and wkb/hexwkb. At the present time, serialize/deserialize and wkb/hexwkb are the same and has possibly caused the blind usage of wkb/hexwkb when serialize/deserialize is appropriate and vice versa.

The key difference between serialize/deserialize and wkb/hexwkb is:

  1. serialize/deserialize: Internal storage format. The output seen from a query like the following should be of this format.
SELECT rast FROM mytable
  1. wkb/hexwkb: Transport format. This format is meant for use by and must be explicitly called for by clients. To get wkb/hexwkb output, the clients must use ST_AsBinary().

The rational for this is so that in the future, these two formats can deviate from each other (particularly the internal storage format).

Change History (4)

comment:1 Changed 5 years ago by dustymugs

I'm expecting this audit to take place for PostGIS 2.2.

comment:2 Changed 5 years ago by dustymugs

Milestone: PostGIS FuturePostGIS 2.2.0

comment:3 Changed 3 years ago by dustymugs

Milestone: PostGIS 2.2.0PostGIS Future

comment:4 Changed 4 months ago by robe

Milestone: PostGIS FuturePostGIS Fund Me

Milestone renamed

Note: See TracTickets for help on using tickets.