Skip to Content
0
Former Member
Apr 12, 2010 at 06:59 AM

Problem with trigger on large varchar field

141 Views

Hello,

I've noticed a strange problem with triggers. I have two tables, first with current data (REQUEST) and the other for change log on the first table :(TRC_REQUEST). The change log contains the same fields as the original table plus fields for User (who has made a change), date and time (when the change took place) and type of the change (Insert, Update, Delete).

Each time my application makes a change in REQUEST table, the triggers defined on the REQUEST table inserts a new record in the change log.

The problem occurs when the original table contains a varchar field longer the 4000 - we've made several tests and it looks like the only reason. When the filed (for description) is shorter or equal to 4000 then everything works as expected. If however we alter it to longer than 4000 then every operation on the original table takes very long and makes the temporary data space grow to infinity (and it finally freezes the dabase when it reaches the maximum data space for our database).

Could anyone confirm this is a bug? For us, the only workaround is to cut the field down to 4000. Of course, our database is non-UNICODE (although the catalog is) so the sinlge row can have the maximum size of 8000.

We've noticed this behaviour after migrating (with the help of loader) our database from 7.4. - with the old version the problem did not exist.

Best regards,

Marcin Pytel

Edited by: Marcin Pytel on Apr 12, 2010 9:03 AM

We use version 7.7.06.09