ContinuouSQL Triggers

Are there certain types of continuous views where continuous triggers work better or worse? I can imagine things like alerts on moving averages could get tricky and possibly send repeated alerts when predefined thresholds are crossed multiple times.

Couple of questions:<p>- If the trigger function hits a service that takes a long time to respond, how does that affect the system?<p>- Why did you have to reimplement trigger functions, what was the problem with using trigger functions for tables on continuous views?

This whole example represents a common workflow in fraud detection (alerts on data that hits a certain pattern). However, when I worked at Braintree, doing this real-time was tough and we&#x27;d analyze stuff retrospectively.

Can you create a trigger on any continuous query