Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: My Binary Experience

Re: My Binary Experience

From: Werner <werner.smit_at_baps.com>
Date: 1997/06/21
Message-ID: <33ACC454.B9B@baps.com>#1/1

Scott Ferrett wrote:

Hi Scott
Thanks for the feedback!

I eventually got it to add nulls! That is with a ADD() statement, and with the Oracle Connect driver supplied by Topspeed.

But 2 minutes after this I found another problem. Although I now can add NULLS, i cannot add any character above 126. aaaaaaaarrrrrrrrggggggghhhhhhhhh!!!!

Oracle decides that it cannot handle higher than 126 in this instance and translate them all to "?" or otherwise known as 63.

Adding them via sqlprop work if you break it down to numbers   chr(127)||chr(128) on and insert statement though... But I would really hate doing that - it's just plain messy..

Any ideas ?

>
> In article <33A90108.3352_at_baps.com>, Werner wrote:
> > You say VARCHAR2 does not allow non-printable character, this is simply
> > not true. You can insert any type of character into a varchar2, if you
> > load SQL*Plus and do a
> > " insert into table1
> > (field1)
> > values
> > ('scott'||chr(0)||'Ferret');"
> > it will work fine, and what's more you can select * from tab1 without
> > the problems
>
> You are correct. I was using ODBCTest to connect to Oracle because I find SQL*Plus to be such a
> painful interface. When I issued the select * from table after doing an ADD() from an Oracle
> Connect program that was inserting a null character I got back a null character. Whilst looking
> at this I realised that it will not work with the ODBC driver as it uses C strings due to
> limitations in ODBC/ODBC backends. You could use your above statement with PROP:SQL to get the
> nulls in with ODBC.
>
> SuRF Down Under
> (TopSpeed R&D)
Received on Sat Jun 21 1997 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US