SPI changes for custom store, dictionary and expression implementations
Implementors of OpenJPA SPI interfaces must recompile and implement new methods: BrokerFactory (createPersistenceStructure, dropPersistenceStructure, validatePersistenceStructure, truncateData; AbstractBrokerFactory throws UnsupportedOperationException by default), ExpressionFactory (newTypecastAsString, newTypecastAsNumber, left, right, replace, getNativeObjectId, version), Result (getInstant, getYear), Select (appendNullsPrecedence, addSetOperatorSQL, getSetOperatorBuffer), OpenJPAConfiguration (schema generation script accessors, isSchemaGenerationExplicit, isSpecCompliantSchemaGeneration) and JDBCConfiguration (get/setSyncMappingsExcludeTypes).
DBDictionary.SerializedData is now a record (bytes() instead of the bytes field); IdentifierRule.setReservedWords takes a Collection and matches case-insensitively, so subclasses overriding the Set variant no longer override; JavaTypes.INSTANT (39) and JavaTypes.YEAR (40) were added and must be handled by custom value handlers and strategies; QueryExpressions gained nullPrecedence, setOperationType and setOperands, which only the JDBC store consumes, so a custom StoreQuery silently ignores NULLS FIRST/LAST and set operations unless it is extended. DBDictionary gained a number of public configuration fields (ReplaceFunctionName, LeftFunctionName, RightFunctionName, NaturalLogarithmFunction, CeilingFunction, ExceptFunction, TypecastToStringTypeName, IntegerCastTypeName, SupportsUnsizedCharOnCast, RequiresCastForExtractOperand) and hooks (isDroppable(Sequence), toJDBCEscapedDateTimeLiteral, appendNullsPrecedence, getExtractField, getExtractDateTimeFieldFunction, get/setMajorVersion, get/setMinorVersion).