ORA-01446 on-update [message #223429] |
Thu, 08 March 2007 20:06 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
tnegrey
Messages: 10 Registered: July 2005 Location: Calgary Co-op
|
Junior Member |
|
|
Hello,
I'm using an 'On-Update trigger' to replace the default Form Builder processing for updated records. When I try to change a column in the form I get:
ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc.
The on-update doesn't fire. How do I get around this. The block is based on a view.
|
|
|
|
Re: ORA-01446 on-update [message #225871 is a reply to message #225420] |
Wed, 21 March 2007 15:44 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
tnegrey
Messages: 10 Registered: July 2005 Location: Calgary Co-op
|
Junior Member |
|
|
I did not solve this problem. I'm still looking, thanks for the information on the 'user_updatable_columns'.
I don't want the form to update the view. If possible, I would like the user to be able to change the columns on the form and the 'new entered data' would be sent to a function (java script) which does the actual update of the tables.
|
|
|
|
|
|
Re: ORA-01446 on-update [message #226907 is a reply to message #226903] |
Mon, 26 March 2007 21:46 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
tnegrey
Messages: 10 Registered: July 2005 Location: Calgary Co-op
|
Junior Member |
|
|
Visual Basic?
We are a Java shop and eventually will convert all Oracle forms to JSP.
Oracle forms is not capable of doing what I'm asking?
|
|
|
|
Re: ORA-01446 on-update [message #475818 is a reply to message #226948] |
Fri, 17 September 2010 16:48 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
|
Hello all!
I suppose that tnegrey don't need this anymore, but I was suffering from the same problem and I found a workaround for it.
This "problem" occurs at the ON-LOCK trigger of the block. When the query data source is a complex view (with distinct or group by), it's not possible to get the rowid to lock the record.
So, if you create a new ON-LOCK trigger (overwriting the default), you can develop your own treatment to lock the record that you will update (or use a simple "null;" statement ).
[]'s
Tocha.
|
|
|
|