Re: PostGIS/ PostGreSQL ODBC problem

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: "TONY J(dot)Y(dot)" <tjiang(at)mrf(dot)com>
Cc: postgis members <postgis(at)yahoogroups(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PostGIS/ PostGreSQL ODBC problem
Date: 2001-12-17 23:54:15
Message-ID: 3C1E85A7.67E74DFA@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> "TONY J.Y." wrote:
>
> Hi all,
>
> I am using the PostGIS to do research. Here I think that I found a bug
> with PostGreSQL / PostGIS.
> PostgreSQL 7.1.3/ PostGIS 0.6.2
>
> There is a function called "Astext" in PostGIS, defined as below.
> -- Function: astext(geometry)
> CREATE FUNCTION "astext"("geometry") RETURNS "text" AS
> 'astext_geometry' LANGUAGE 'C' WITH (ISSTRICT);
> When I used this function to return a geometry column, everything is
> OK if the result was less than 8190.
> I used the ODBC to get the ADO RecordSet. The DefinedSize of the
> field "astext" is 8190.
>
> Does this the PostgreSQL's ODBC problem? If the ODBC can not get the
> field's size, would it give the size of 8190?

Are you using the psqlodbc driver whose version >= 7.01.0006 ?
If so you could increase the size(8190) by setting MaxLongVarChar
driver option using ODBC DataSource Administarator.
You may be able to set the size to 0(unlimited?).

regards,
Hiroshi Inoue

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Hill 2001-12-18 01:58:49 Strange pg_oid problem.
Previous Message TONY J.Y. 2001-12-17 21:42:50 PostGIS/ PostGreSQL ODBC problem