public Class SymfowarePlatform

http://wiki.eclipse.org/EclipseLink/Development/Incubator/Extensions/SymfowarePlatform
Test results: http://wiki.eclipse.org/EclipseLink/Development/DatabasePlatform/SymfowarePlatform/TestResults
Contributed by: Fujitsu Ltd.
Contributed under bug: 288715

Feature Testing

• DDL Generation - Succeeds
• Outer Join - Succeeds
• Subquery - Succeeds with Limitations
• Stored Procedure Calls - Succeeds
• Stored Procedure Generation - Succeeds
• Native Sequences/Identifier fields - Succeeds
• JPA Bulk Update/Delete - Succeeds with Limitations
• Batch Reading - Succeeds
• Batch Writing - Succeeds
• Pessimistic Locking - Succeeds with Limitations
• First Result/Limit - Succeeds with Limitations
• Expression Framework - Succeeds with Limitations
• Delimiters - Succeeds
• Auto Detection - Succeeds

Limitations

• Reserved SQL keywords cannot be used as table, column or sequence names. Use a different name, or enclose the name in double quotes. For example: @Column(name="\"LANGUAGE\"")
• Spaces cannot be used in table, column or sequence names. (bug 304906)
• Input parameters cannot be used as first two arguments to the LOCATE function at the same time. (bug 304897)
• The first argument to the SUBSTRING function cannot be an input parameter. (bug 304897)
• Input parameters cannot be used as adjacent arguments to the CONCAT function. Concatenate the values in Java code first and pass the result to the query instead. (bug 304897)
• Input parameters cannot be used at both sides of an operand at the same time in an SQL statement (e.g. '? * ?'). Perform the operation in Java code first and pass the result to the query instead.
• Identity fields cannot be used. When primary key generation type IDENTITY is specified, a database sequence will be used instead.
• Pessimistic Locking adds 'FOR UPDATE' to the SELECT statement, and cannot be used with queries that use DISTINCT. (bug 304903)
• Pessimistic Locking cannot be used with queries that select from multiple tables. (bug 304903)
• The LockNoWait option of Pessimistic Locking cannot be used; it is ignored when specified (i.e. only 'FOR UPDATE' is added to the SELECT statement).
• Query timeout cannot be used; the timeout value is silently ignored. (bug 304905)
• Bulk update and delete operations that require multiple tables to be accessed cannot be used (e.g. bulk operation on an entity that is part of an inheritance hierarchy, UpdateAll and DeleteAll queries). (See bug 298193).
• Dropping of tables, sequences and procedures while the database connection is still open can fail due to unreleased locks. Shut down the Java process that executed the create operation before performing the drop operation, or have the create operation use an unpooled connection that is closed after use (GlassFish's deploy-time table generation function uses an unpooled connection).
• The standard deviation (STDDEV) and variance (VARIANCE) functions cannot be used. (bug 304909)
• '= NULL' and '<> NULL' cannot be used for null comparisons in the WHERE clause. Use 'IS (NOT) NULL' instead.
• A scrollable cursor policy of CONCUR_UPDATABLE mode cannot be used with queries that select from multiple tables.
• Columns and literals of different type may need casting to allow them to be compared or assigned. (bug 372178) For example: 'SELECT ... WHERE CAST(PHONE_ORDER_VARCHAR AS INTEGER) BETWEEN 0 AND 1'
• Subqueries with joins to the outer query are not supported. (see rfe 298193)
• Stored functions are not supported. (bug 342409)
• Using subquery in select list for query specification or single-row SELECT statement is not allowed. (bug 372172)
• The CascadeOnDelete doesn't work on a relation where CascadeType.Remove or CascadeType.All is specified. (bug 342413)
• A subquery cannot be specified on both sides of a comparison predicate or a quantified predicate. (bug 378313)
• A base table name to be updated cannot be identical to table name in from clause in query or subquery specification (bug 381302)

Additional Notes

• When using DDL generation, indices are automatically generated for primary and unique keys.
• The MOD(x, y) function is executed as 'CASE WHEN y = 0 THEN x ELSE (x - y * TRUNC( x / y )) END' on Symfoware database, which gives the same result as the MOD function on Oracle database. Input parameters cannot be used for both its arguments at the same time. In such case, calculate the modulus in Java code first and pass the result to the query instead.
• When input parameters are used as arguments to the TRIM function, they are substituted with their values before the SQL statement is sent to the JDBC driver.
• When an input parameter is used as argument to the UPPER, LOWER or LENGTH functions, it is substituted with its value before the SQL statement is sent to the JDBC driver.