Re: psqlODBC text length with no records

Parse statement(C0 in the connection string) has no effect on this.

> With theB0(Max varchar)=254 setting, Postgres for lengths=0 or null returns a "Memo"
>    In vfp, when displayed to the user in a grid, "Memo" is shown in
> the field instead of the value

Any other settings that may help?


-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@aklaver.com]
Sent: Wednesday, May 14, 2014 12:19 PM
To: Barry Bell; Hiroshi Saito; Michael Paquier; Hiroshi Inoue
Cc: Heikki Linnakangas; Anna Gershnik; pgsql-odbc@postgresql.org
Subject: Re: [ODBC] psqlODBC text length with no records

On 05/14/2014 09:08 AM, Barry Bell wrote:
> None of the below information helps because we are taking the output
> cursor  From the postgrest sql,  putting it into a VFP grid and displaying to the user.
>
> With theB0(Max varchar)=254 setting, Postgres for lengths 1-254 returns a "char"
>    In vfp, when displayed to the user in a  grid, the value of field
> is shown
>
> With theB0(Max varchar)=254 setting, Postgres for lengths=0 or null returns a "Memo"
>    In vfp, when displayed to the user in a grid, "Memo" is shown in
> the field instead of the value
>
> With theB0(Max varchar)=254 setting, Postgres for length over 256 returns a "Memo"
>    In vfp, when displayed to the user in a grid, "Memo" is shown in
> the field instead of the value We only have some code after the sql that sorts the cursor and VFP is unable to sort
onthe MEMO fields. 
>
> Our issue is when Postgres is returning a fireld with 0 or null
> length, The driver is not using the B0(Max varchar) setting.

Well you could always try Parse Statements:

http://psqlodbc.projects.pgfoundry.org/docs/config.html

>
> Barry Bell
> Senior Developer/Analyst

--
Adrian Klaver
adrian.klaver@aklaver.com