Newsgroups: comp.databases.oracle.misc
Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.cc.ukans.edu!newsxfer.eecs.umich.edu!newsfeed.mathworks.com!nntp.abs.net!ash.uu.net!xyzzy!nntp
From: Rajesh Patel <rpatel@rajix.com>
Subject: Views and Inserts
X-Nntp-Posting-Host: a-r1tdon4kf0fhj.mw.nos.boeing.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Message-ID: <401E82B0.4000102@rajix.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Sender: nntp@news.boeing.com (Boeing NNTP News Access)
Content-Transfer-Encoding: 7bit
Organization: The Boeing Company
X-Accept-Language: en-us, en
Mime-Version: 1.0
Date: Mon, 2 Feb 2004 17:02:40 GMT
Lines: 20
Xref: newssvr20.news.prodigy.com comp.databases.oracle.misc:135256

I have an existing database that i cannot change, unfortunately
they have used CHAR instead of VARCHAR, so we
are going to have to code around the right padding
issues.

I attempted to remedy this by using a view and using
TRIM to get rid of the padding, however when I do
an insert on the trimmed fields I get:

[WARN] JDBCExceptionReporter - -SQL Error: 1733, SQLState: 42000
[ERROR] JDBCExceptionReporter - -ORA-01733: virtual column not allowed here

I take this to mean that when trimmed those fields the database lost
the link to the underlying table.  If I remove the trim statments
from the view inserts work correctly.

Any Ideas?  Strategies to get around this issues?

Raj