Data Types in 8.00.01.02

This is a multi-part message in MIME format.

------_=_NextPart_001_01C647BB.B45ACE39
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In BusinessObjects XI Business View Manager, any varchar() field
larger than varchar(254) shows up as a "Persistent Memo" type. Is this
because the ODBC driver is doing something funny when it sends over
metadata, or is this a BOXI issue?

__
David B. Held
Software Engineer/Array Services Group
200 14th Ave. East, Sartell, MN 56377
320.534.3637 320.253.7800 800.752.8129


------_=_NextPart_001_01C647BB.B45ACE39
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable




charset=3Diso-8859-1">
6.0.6617.29">

In BusinessObjects XI Business View =
Manager, any varchar() field


larger than varchar(254) shows up as a =
"Persistent Memo" type.  Is this


because the ODBC driver is doing =
something funny when it sends over


metadata, or is this a BOXI =
issue?

__


David B. Held


Software Engineer/Array Services =
Group


200 14th Ave. East,  =
Sartell, MN 56377


320.534.3637 320.253.7800 =
800.752.8129

Re: Data Types in 8.00.01.02

> In BusinessObjects XI Business View Manager, any varchar() field
> larger than varchar(254) shows up as a "Persistent Memo" type. Is this
> because the ODBC driver is doing something funny when it sends over
> metadata, or is this a BOXI issue?

The ODBC driver the best what it can. But yes the problem is on PgSQL and
psqlODBC driver side. When ODBC driver ask for result types PgSQL backend
answer text type. This is the real "problem".

You are able to change quite the behaviour with setting Max Varchar (size).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly