[postgis-users] Problem with PostGIS 1.0.0 RC1

Mark Cave-Ayland m.cave-ayland at webbased.co.uk
Mon Jan 24 01:47:52 PST 2005

> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net 
> [mailto:postgis-users-bounces at postgis.refractions.net] On 
> Behalf Of strk at refractions.net
> Sent: 23 January 2005 09:11
> To: Markus Schaber; Mark Cave-Ayland
> Cc: PostGIS Users Discussion
> Subject: Re: [postgis-users] Problem with PostGIS 1.0.0 RC1


> The only *transparent* way would be having geometry_in 
> recognize all of HEXWKB,bytea,WKT (currently only bytea missing).

Hmmmm so it looks like the PostgreSQL type system can't handle this in the
way I was expecting :(

Given that changing GeomFromWKB from WKBHEX to bytea will already break
existing applications, how about a new function GeomFrom(E)WKBHEX(text) that
takes HEXWKB input and leaving GeomFrom(E)WKB(bytea) as it is? Is there then
any need to have geometry_in accept HEXWKB? (I understand that we need to
keep WKT as a hack so that dumps from older versions of PostGIS can be

Kind regards,


WebBased Ltd
South West Technology Centre
Tamar Science Park
PL6 8BT 

T: +44 (0)1752 791021
F: +44 (0)1752 791023
W: http://www.webbased.co.uk

More information about the postgis-users mailing list