 | |
Oracle Trigger Late binding
comp.databases.oracle.misc comp.databases.oracle.misc
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: Oracle Trigger Late binding -
04-17-2008
, 02:33 PM
|
On Apr 17, 7:32 am, Vabs <rajat... (AT) gmail (DOT) com> wrote: i want to use if(:new.column_name is not null) which works perfect... however my problem is that i want to set this column_name as a run time variable (as the table columns are not known to me) I tried using a variable but oracle throws a PLS-00049 bad bind variable error. Please help... Why do you 'need' this? It seems like a bad idea to me; the :new and  ld 'blocks' aren't available outside of a trigger which iswritten against a specific table (and you should know the columns for that table if you're writing a trigger against it). I really see no purpose in what you're asking. David Fitzjarrell The Quest for the Universal Application? |
#12
| |||
| |||
|
|
On Apr 17, 7:32 am, Vabs <rajat... (AT) gmail (DOT) com> wrote: i want to use if(:new.column_name is not null) which works perfect... however my problem is that i want to set this column_name as a run time variable (as the table columns are not known to me) I tried using a variable but oracle throws a PLS-00049 bad bind variable error. Please help... Why do you 'need' this? It seems like a bad idea to me; the :new and ld 'blocks' aren't available outside of a trigger which iswritten against a specific table (and you should know the columns for that table if you're writing a trigger against it). I really see no purpose in what you're asking. David Fitzjarrell The Quest for the Universal Application? |
#13
| |||
| |||
|
|
On Apr 17, 7:32 am, Vabs <rajat... (AT) gmail (DOT) com> wrote: i want to use if(:new.column_name is not null) which works perfect... however my problem is that i want to set this column_name as a run time variable (as the table columns are not known to me) I tried using a variable but oracle throws a PLS-00049 bad bind variable error. Please help... Why do you 'need' this? It seems like a bad idea to me; the :new and ld 'blocks' aren't available outside of a trigger which iswritten against a specific table (and you should know the columns for that table if you're writing a trigger against it). I really see no purpose in what you're asking. David Fitzjarrell The Quest for the Universal Application? |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.