Comments on Grassroots Oracle: Compound primary keys in Application Express

Matt, Scott, Instead of triggers offered a very f...

2012-01-27T15:56:55.011+08:00

Matt, Scott,

Instead of triggers offered a very flexible solution for tabular forms in APEX until 3.2. But from 4.1 you need to have a have a key-preserved table joined in your view to make it work. Have a look at my (slightly outdated) post on "Tabular Forms on Complex Views - using INSTEAD OF Triggers".

Cheers,
Christian

Hi Matt, I did consider "instead of" tr...

2012-01-25T12:34:38.441+08:00

Hi Matt,

I did consider "instead of" triggers at one point, but most have forgotten about it by the time I wrote up the post. I might investigate that further later,

Cheers

Hi Scott I was wondering whether you considered c...

2012-01-25T09:49:16.786+08:00

Hi Scott

I was wondering whether you considered creating "instead of" triggers on the view.

This way you could keep your automatic row processing process and APEX would still do all the concurrent update checking. You can then control how the data is saved in the trigger, i.e. ignoring your rowid column and any others that might be read only etc.

I haven't tested this so I'm not sure, but it was just a thought after reading your post.

P.S. Sorry to hear about your mate.

Matt