Re: REPOST: Copying a LONG via Trigger?

We've no choice but to use longs, as we're only on Oracle73, and we've got existing data to migrate that has as much as 6 or 7k in some fields. There are ways to deal with longs, but in a trigger you're very limited.

nbc

On Mon, 15 Mar 1999 09:17:27 -0700 Ken Rachynski <krachyn_at_cadvision.com> wrote:

>Nicholas,
>
>I have recently discovered that, but this was an old system that got migrated to Oracle. At
>the time of the migration, LONG sounded like it best fit my needs.
>
>I did some further testing last week and discovered that the front-end that I'm using (Paradox
>7) does not like CLOBs very much which means that I'm stuck using manual routines to archive
>each record instead of a nice neat trigger. On the plus side, I have only one table that uses
>a LONG so I don't have to do too much work around this issue.
>
>With luck, I'll get to rewrite everything in Delphi sooner than later and I'll have full
>control over what data types to use.
>
>Nicholas Couch wrote:
>
>> I've been wrestling with this problem myself recently. You can't use :old or :new on a
>> long column. In fact, there are quite a few things you can't do with longs. I wish I had a
>> workaround for you. In Oracle8 you can use BLOB data types, which don't have all the
>> restrictions of longs.
>>
>> nbc
>
>--
>Ken Rachynski
>Database Analyst
>krachyn_at_cadvision.com
><http://www.cadvision.com/krachyn>
>ICQ: 3113514
>
>
Received on Tue Mar 16 1999 - 11:47:45 CST