Suggested Triggers & Functions Naming Convention?
От | Bruno Lavoie |
---|---|
Тема | Suggested Triggers & Functions Naming Convention? |
Дата | |
Msg-id | 6d48544304103114081acb5528@mail.gmail.com обсуждение исходный текст |
Список | pgsql-general |
Hello, 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 function) 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? OR why postgresql triggers must call functions? IMO: - 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 Bruno
В списке pgsql-general по дате отправления: