Plex 6.0
From Plex-XML
Plex-XML has been updated and is ready for use with Plex 6.0
- Exec SQL in 6.0
Unfortunately the implementation of the ExecSQL processing in the Plex Java runtime has some fundamental changes comparing to Plex 5.5. In Plex 6.0 the new behavior is
- the ExecSQL source code will be used for an SQL prepare statement. But in our complete flexible generated SQL statements the source code consist of one parameter only. This will cause the prepare statement fail to run and return with an error.
- source code parameters will be passed to the SQL prepare statement
We have implemented a very flexible use of SQL while we generate our complete SQL statements at runtime. In order to be able to do this with Plex 6.0 we needed to bring back the old parameter handling behavior into the Plex 6.0 Java runtime. So we need to skip the prepare statement in the runtime. We have implemented this in the runtime in case the source code starts with a parameter. This limitation is reported to CA as Problem# 1216. Plex 6.0 SP1 solves this issue (see below).
- Plex 6.0 Build 47.006
- From Plex 6.0 Build 47.006 there is a new Triple "SRC SQL Statement type Prepared or Unprepared which - set to Unprepared - solves the issue
- For PleXML you have to unset the Flag "use field implementation names in Java source" in the Generation Options*
- Things to do in your Eclipse Project when upgrading to 6.0 Build 47.006
- remove all generated Beans/Handlers
- do a rebuild
- regenerate Beans/Handlers
- Pitfalls you should beware of
- Do not map Fields of Array Variables as Format Message Parameters : Plex will crash ( we should open a case at CA!)
- Do not use Variables with same Name (from different Group Models, one as local, one as input) within a Function for which you want beans to be generated since one of them will be renamed in the generated code
- Other useful new options found in Plex 6.0
- SQL/Fetch-Function now has a "Maximum Recordset Size Option"
