Re: SPL & Triggers - do's and don'ts

In article <3291472D.5831@sprynet.com>, Jake Salomon <jsalomon@sprynet.com> writes >As far as I recall, the SP cache is still limited to 50 procs. This is >not [yet] a tunable to keep those feature requests coming, folks! > Where did you hear about this limit - I cannot find it in the manuals. >Just remember that SPL is meant to "encapsulate" compound database >statements. Excessive use for programming is hazardous to your >benchmarks. > Exactly. SPL is do suppose to allow a lot of complex logic but to a) allow a group of SQL statements to be executed in one go. (Stored procedures). This is to reduce traffic between the engine and the front-end process. b) allow intelligent processing when something in the database changes. i.e. triggers to stop 'invalid' changes to the database. >> We have invested in Informix training courses, read the manuals and >> bought the only book on the market place about this subject - any >> suggestions based on development experience would be much appreciated. > Use SPL sparingly. It's not meant to do everything you could possibly want to do. It is just another tool. -- David Williams