<= Previous | Next => | Table of Contents | DataVision FAQ |
Any database that has a JDBC driver. This means PostgreSQL, MySQL, Informix, Oracle, hsqldb, Microsoft Access, and more.
As of version 0.2.1, DataVision has stopped relying upon the more advanced JDBC features it used. This means that pretty much any JDBC driver should work.
For information about driver names and connection info string formats see your database's JDBC driver documentation. Some suggestions also appear in the DataVision User's Manual.
Data access is currently tied to JDBC, but I want to separate that layer so data can come from any source that conforms to some API: JDBC, text files, streams, XML, whatever.
In the mean time, someone could implement a non-JDBC solution fairly easily. There are only two or three methods in the Report class that need overriding, and ReportReader (the XML report description reader) would need to be modified to ignore the database and query tags. Remove references to the Database and Query classes from Report, and---voilá!---you can access the data source of your choice.
No. The problem with binary fields is that there is no way for DataVision to know what is in the field: text, an image, music. Even if you told it what the field contains, DataVision would then have to know about every image, music, or text format in order to display it properly.
Some users have had problems with drivers earlier than 2.0.11. You can find the latest version of the MM.MySQL driver from that project's SourceForge downloads page.
<= Previous | Next => | Table of Contents |