> Supporting special constructors is a
> workaround, the real problem is: 'how to pass data to a trigger'.
Yes, you are right it is more general case but I really need only
initialization parameters.
> What about...
I've thought about such approach with only the difference that in my
case parameters should be persistent, so should be stored in table..
Yes, this should work but maintaining this table is not very elegant
solution I think. I prefer to allow database do dirty work by itself.
So my desire was to solve this once and forever and good if for other
users too. May be its possible to do this in a common way somehow? For
example add extended trigger interface like that:
public interface ParametrizedTrigger extends Trigger {
void setParameters(ResultSet rs);
}
and add to sql something like "create trigger .... with parameters
select 123,'aaa', null from dual where 1>2" and also "alter
trigger ... set parameters select ...."
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en
-~----------~----~----~----~------~----~------~--~---
