carriage return / newline chars in varchar fields ... 7.31FC2 on Tru64 barfs
Posted in 2000
Topics: Connectivity: ODBC / JDBC / .NET, Data Types & Schema Design, Platform-Specific Issues
Hi all,
In my never ending question to get Informix to sing and dance, I'm
running into a weird problem on 7.31FC2 on Tru64 that I don't see on
7.30TC7 on NT, or 7.30UC4 (?) on Linux.
When I try to insert into a varchar field via ODBC (both the 2.80 and
3.30 drivers ... not the 3.31 driver that has a similar problem),
something like
insert into newlinetest values ('this text has
a carriage return')
It barfs with the 202 illegal character message. Now I know on IFS
2000 9.20 (NT, Solaris or Linux) that the db needs ifx_allow_newline
run to get this to behave, but I can't see why this is dying on 7.31,
as it's working fine on other 7.30 platforms.
Is there anything weird about the Tru64 implementation of 7.31 that
might cause this, or anything like ifx_allow_newline that I need to
run to make it behave.
Ciao
Fuzzy
;-)
On Thu, 05 Oct 2000 06:29:46 GMT,
granta@nospam.student.canberra.edu.au (Fuzzy) wrote:
>Hi all,
>
>In my never ending question to get Informix to sing and dance, I'm
>running into a weird problem on 7.31FC2 on Tru64 that I don't see on
>7.30TC7 on NT, or 7.30UC4 (?) on Linux.
>
>When I try to insert into a varchar field via ODBC (both the 2.80 and
>3.30 drivers ... not the 3.31 driver that has a similar problem),
>something like
>
>insert into newlinetest values ('this text has
>a carriage return')>
>It barfs with the 202 illegal character message. Now I know on IFS
>2000 9.20 (NT, Solaris or Linux) that the db needs ifx_allow_newline
>run to get this to behave, but I can't see why this is dying on 7.31,
>as it's working fine on other 7.30 platforms.
>
>Is there anything weird about the Tru64 implementation of 7.31 that
>might cause this, or anything like ifx_allow_newline that I need to
>run to make it behave.
>
>Ciao
>Fuzzy
>;-)
Me again. Seems all 7.3x servers have a problem with 2.80, 3.30 and
3.31 clients (and 3.32 still has the problem if escaped quotes are
used). Sorry for the false info.
Winding back to the 2.50 client fixed everything. Anyone care to bet
if any of the 3.3x clients will ever work?
:-)
Ciao
Fuzzy
:-)