| [birt-pmc] ODA Updates |
|
Are we having
a PMC today, I seem to remember that we are deferring this weeks
activities. In any case, I have an issue that I want to run by the PMC. One of my consultants has been working with the jdbc ODA and has a series of enhancements that we would like to make to the existing jdbc ODA. The list of enhancements are: a) Support for Named Parameters. The jdbc specification does not provide support for named parameters out of the box. Steve has created a relatively simple substitution system that converts named parameters into simple parameters. We have actually used this system at a client and it worked very well. I believe that this would really make the jdbc ODA more functional. b) Support for SQL Dialects There are basic differences between the many SQL dialects. For example Oracle uses NVL, TransactSql uses IsNull. Steve has created a property template that allows a developer to specify substitution rules which will translate between SQL dialects. This means that the same sql query can be used against multiple sql servers and still support the subtle differences in the SQL dialects. c) Re-Factor jdbc UI There are several methods in the oda.jdbc.ui that access the java.sql.* classes directly as opposed to using the oda.jdbc runtime classes. When this happens it makes it difficult for someone to extend the oda.jdbc runtime only, which should be relatively straight-forward. Instead the user has to modify both the oda.jdbc and the oda.jdbc.ui packages. Wanted to know the best way to handle this. Should it be done as one bugzilla entry with code submissions attached to it? Should it be done as three (or more) bugzilla entries? Should it be done as a sub-project proposal? We can probably handle this through email if we are not having PMC today. Thanks, Scott |