Trigger on CLOB

[Sachin]

I have a table with a CLOB column with a INSERT / UPDATE/DELETE trigger on it so that anything that is done on that table is replicated into a *_CLONE table.

If I fire an insert via the Command Window or sqlplus, the clob column is duplicated properly in the clone table.

But, if I use the Edit Data feature and insert a new row, the clob column is blank in the clone table. However, the main table has the proper value.

If this is a bug, can this be fixed ASAP?

Thanks,

 

[Marco Kalter]

This is caused by the fact that the SQL Window writes the CLOB data after initially writing an empty_clob() and returning the new LOB Locator. This ensures compatibility with Oracle 8.0.x, which does not know the Temporary CLOB data type required to directly write the CLOB data.

We can enhance this for 8.1 and later so that it writes the LOB data directly with the insert/update statement. I have added this to the list of enhancement requests.

 

[Sachin]

We can enhance this for 8.1 and later so that it writes the LOB data directly with the insert/update statement. I have added this to the list of enhancement requests.

After 8.1 seems pretty far away! So what is the workaround - to fire insert statements manually?
Can't this fix be done earlier - this is really killing me and my team.

 

[Marco Kalter]

I meant Oracle 8.1 and later (which introduced temporary CLOB's). Not PL/SQL Developer 8.1.

 

[Sachin]

Marco,

Will this be incorporated in the 8.0 final or RC ?

Thanks,

 

[Marco Kalter]

This is indeed still on the to-do list.

 

[Sachin]

Any updates on this one? I thought this was going to be included in 8.0?

 

[Marco Kalter]

That was the plan, but it has been postponed to a 8.0.x release.

 

[Dawn]

Could I get a status of what version this enhancement will be included in?

Thanks, Dawn

 

[Marco Kalter]

This will be in 8.0.1.