From be068f44b280072d34e79df3ab97a8af4eb97251 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Sat, 28 Nov 2009 06:50:32 +0000 Subject: [PATCH] slight amendment to description of casts git-svn-id: http://svn.osgeo.org/postgis/trunk@4925 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/reference_type.xml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/reference_type.xml b/doc/reference_type.xml index 5c19dded8..57be6f171 100644 --- a/doc/reference_type.xml +++ b/doc/reference_type.xml @@ -12,6 +12,8 @@ The danger of relying on automatic cast behavior is when you have an overloaded function say one that takes a box2d and one that takes a box3d but no geometry. What happens is that both functions are equally good to use with geometry since geometry has an autocast for both -- so you end up with an ambiguous function error. To force PostgreSQL to choose, you do a CAST(mygeom As box3d) or mygeom::box3d. + + At least asof PostgreSQL 8.3 - Everything can be CAST to text (presumably because of the magical unknown type), so no defined CASTS for that need to be present for you to CAST an object to text. -- 2.50.1