Re: SQL*Plus Copy Command Question

From: Christopher Jones <cjones_at_au.oracle.com>
Date: 1995/09/24
Message-ID: <x768ijyvtk.fsf_at_hurrah.au.oracle.com>#1/1


In article <43r6f6$lqf_at_fred.cas-ps.com> rek_at_cas-ps.com (Reinhard Kuhn) writes:

> The problem is not that Oracle recognizes a space sometimes as valid data
> and sometimes not. A space is always recognized as valid data. However
> Oracle in it's infinite wisdom decided, that an empty string ('') equals to
> NULL. So whenever your data is trimmed (which seems to be the case in
> sql*plus copy), Oracle will consider a space as NULL-value and refuse to
> insert it in a 'not null' column.
> Admittedly this behaviour is quite ugly (and I personally consider it to
> be a bug) but I'm afraid that Oracle doesn't intend to change it in future
> releases, so you will have to work around it.

We don't _intend_ to fix the COPY command: it has already been fixed. Trailing whitespace in VARCHAR2 columns is no longer trimmed. The reference is bug 158316.

Chris

--
Christopher Jones, cjones_at_au.oracle.com

-- 
Christopher Jones, cjones_at_au.oracle.com
Received on Sun Sep 24 1995 - 00:00:00 CEST

Original text of this message