Release-Notes.md
... ...
@@ -5,6 +5,7 @@
5 5
##Features
6 6
|Case|Category|SubCategory|Description|
7 7
|:----|:---------------|:---------------|:---------------|
8
+|HF:22762|Security|License Conflict|Hotfix patch to Izenda 6.10.0.1 to resolve a licensing conflict.|
8 9
|FB:22008|Framework|.NET Version Update |**Updated the Izenda .NET framework to 4.0**|
9 10
|FB:13917|Data|Data Sources|Feature - Addition of support for Oracle Stored Procedures. The only stored procedures supported at this time are pipelined functions that return a table-valued object. See [[this documentation|http://docs.oracle.com/cd/B19306_01/appdev.102/b14289/dcitblfns.htm]] for more details on table-valued pipelined functions. Functionally, these work just like MSSQL stored procedures as far as Izenda is concerned. The processes for including them in VisibleDataSources, working with constraints, passing parameters as filters, etc are the same.|
10 11
|FB:21959|Data|Data Sources|Feature - Addition of MySQL Stored Procedure support. The only stored procedures supported at this time MUST be formatted a specific way for Izenda to be able to use them. The connection string must use the MULTI_STATEMENTS=1 identifier. The procedures themselves must use the following syntax: DELIMITER $$ BEGIN DROP TABLE IF EXISTS `[SprocName]_spResult`; /* Izenda-specific code */ CREATE TEMPORARY TABLE `[SprocName]_spResult` AS /* Izenda-specific code */ [The normal sproc body goes here] SELECT * FROM `[SprocName]_spResult`; /* Izenda-specific code */ END$$ DELIMITER ; where [SprocName] is the exact name of your stored procedure without the brackets. Functionally, these work just like MSSQL stored procedures as far as Izenda is concerned. The processes for including them in VisibleDataSources, working with constraints, passing parameters as filters, etc are the same. Be sure to change the DELIMITER to something other than the semicolon or else MySQL will not correctly compile the stored procedure.|