On 26.5.2010 0:19, James Gregurich wrote:
as a side point.... if you go by name, you have the ability to easily
and precisely re-order the triggers in the future.
Quite true, James.
Name gives a handle to the object that can be utilized.
So I can give my +1 to name based trigger sorting, no problem.
The reason I was promoting the creation order is that it has served me
quite well (in derby)
when building my data model...one table on top of the others.
One at a time.
Where those tables/views rely on the ones that have been already created.
But there certainly exists use cases I have not yet even dreamed of.
- rami
On May 25, 2010, at 1:53 PM, Rami Ojares wrote:
\"
Actually I like the PostgreSQL behavior. So far I don't know about
other databases.
I would side on sql and derby.
But name based order is fine.
Then you just name the triggers so that they collate into a proper
order by using for example an index number.
--
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.
--
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.
