[ 
http://issues.apache.org/jira/browse/DERBY-97?page=comments#action_12313206 ] 

Daniel John Debrunner commented on DERBY-97:
--------------------------------------------

Revision 189858 is the last revision for JSR169.

The functionality differs from the spec (20050201) in three ways:

------

1) Diagnostic tables are not supported in JSR 169

2) Triggers are not supported in JSR169

3)  DECIMAL parameters do not have a mapping into a Java  object for 
procedure/function parameters or return types.

------
1) and 2) are due to those features relying on internally on VTI which 
currently has dependencies on BigDecimal. These need a easily downloadable 
JSR169 jar file to proceed. I don't want to limit the ability to build Derby at 
this point.

3) I now think is the correct approach, otherwise I beleive the behaviour under 
JSR169 would not be in line with the SQL standard and would have different 
behaviour between JSR169 and J2SE/J2EE

Also the test harness is running under JSR169 and the tests that should run 
seem to pass. I need to look at the failures to see they are expected, from 
checks so far they are, e.g. tests fail due to DriverManager, Driver or 
BigDecimal not being found. I then need to add exclude flags for those tests 
and suites that need to be skipped in JSR169.

> Support J2ME/CDC/Foundation with JSR169 JDBC subset
> ---------------------------------------------------
>
>          Key: DERBY-97
>          URL: http://issues.apache.org/jira/browse/DERBY-97
>      Project: Derby
>         Type: New Feature
>   Components: Tools, JDBC
>     Reporter: Daniel John Debrunner
>     Assignee: Daniel John Debrunner
>      Fix For: 10.1.0.0
>  Attachments: derbyJSR169Design.html, derbyJSR169Spec.htm, 
> derbyJSR169Spec_20050210.htm
>
> Add support for Derby running in J2ME/CDC/Foundation platform
> JDBC API defined by JDBC Optional Package for CDC/Foundation Profile (JSR169).
> See functional spec attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to