Most triggers are of the format:
BEFORE [INSERT|UPDATE]
SELECT ... INTO ..
Or
INSERT ..
Or
UPDATE ..
There are some stored procedures that are time specific, yes, daily
reporting rollup and the like, although I don't know to what degree
(secs,mins,hours) (I'm not the DBA who wrote them or that versed in
oracle DBAing), I'll have to ask the former DBA.
There are one or two that use SYSTIMESTAMP, I'm guessing that could be
changed to be done at the app level. Not sure what other oracle-specific
datetime keywords to look out for to be honest.
Thanx,
-Tony
---------------------------
Manager, IT Operations
Format Dynamics, Inc.
303-573-1800x27
[EMAIL PROTECTED]
http://www.formatdynamics.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Cecchet
Sent: Wednesday, July 02, 2008 1:08 PM
To: Sequoia general mailing list
Subject: Re: [Sequoia] sequoia and oracle success
Tony,
> Anybody here using sequoia 2.10 with oracle 10g and using
> triggers/stored procedures with good success?
>
Triggers are not supported in Sequoia 2.10. What kind of operations are
you performing in the triggers?
Stored procedures need to have a deterministic execution. If you are
using things such as date macros they have to be passed as parameters of
the stored procedures.
Keep us posted with your findings,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
