cipher-naught wrote on Friday, July 20, 2012:
Are Triggers, Views, Stored Procedures, etc possible?
From our discussions on possible Demographic Improvments, I wanted to update a discussion from 18 months ago about Trigers and Stored Procedures.
I am not sure how to kick off this discussion. There is a definite discussion of “Are Triggers, Views, Stored Procedures, etc needed?”, but I wanted to start a discussion of “Are Triggers, Views, Stored Procedures, etc possible?”.
I think the first questions from looking through the previous discussion broke down into concerns about:
* Will using Triggers, Views, Stored Procedures, etc (VT-SP) limit OpenEMRs database support?
* Will using VT-SPs limit Shared Hosting options that some users use?
My research looks like the answer is No.
This is what I found (wiki:
• MySQL – All (View, Triggers, and Stored Procedures)
• Oracle – All (View, Triggers, and Stored Procedures)
• PostgreSQL – All (View, Triggers, and Stored Procedures)
• MS SQL - All (View, Triggers, and Stored Procedures)
• DB2 - All (View, Triggers, and Stored Procedures)
• SQLite - Triggers, Views, no stored procedures. (I don’t think people are thinking of moving OpenEMR to SQLite, but wanted to include it.)
Hosting Provider support for MySQL Stored Procedures for shared hosting. I couldn’t find a list of Hosting Provider market share, but these have been listed as Large Hosting Providers.
• Go Daddy – Yes (Stored Procedure Support), but PHP code has to create the Stored Procedures
• Dreamhost – Yes
• Media Temple - No Stored Procedures
• Host Gator - Yes, but may require support email to get turned on.
• Blue Host - Not sure, but appears like Go Daddy
Looks to me that there is little concern about supporting Views, Triggers, and Stored Procedures from the Shared Hosting database support. What does everyone else think?
-cipher-naught
PS I will open another discussion on “Are Views, Triggers, and Stored Procedures worth it” later.