469,344 Members | 6,496 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,344 developers. It's quick & easy.

Suggested Triggers & Functions Naming Convention?


i'm etablishing a naming convention for a new project under
postgresql. For tables, sequences, views, that's ok! I used good
naming conventions for this in the past and i'll keep these rules for
the new project.

but, i plan to use a lot of triggers and functions in this project,
but I'm confused! I know that triggers call already created functions.
But for tracking i must be able to associate these 2 different object
(IMO; from oracle world a trigger is a trigger, a function is a

is someone have a good way to name normal functions & procedures,
triggers, trigger functions (function called by triggers)? because,
when i'll list all functions i dont want to be confused with the
complete list.

why is postgresql is not separing code from triggers and functions as
oracle do?
why postgresql triggers must call functions?

- a function is not defined to be called by a trigger (but a trigger
body can call functions)
- a function intended to be a trigger cannot be called in a select
clause (can i do it in postgres?)
thanx a lot to help me

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?


Nov 23 '05 #1
0 3779

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

27 posts views Thread by Derek | last post: by
4 posts views Thread by Mark Broadbent | last post: by
11 posts views Thread by tonicvodka | last post: by
12 posts views Thread by Telmo Costa | last post: by
114 posts views Thread by Jonathan Wood | last post: by
35 posts views Thread by Smithers | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.