Free dbf jdbc software for linux

DBD::JDBC is a JDBC proxy driver for the DBI module.

SYNOPSIS

use DBI;

$dbh = DBI->connect("dbi:JDBC:hostname=$hostname;port=$port;url=$url",
$user, $password);

# See the DBI module documentation.

DBD::JDBC is a Perl module which works in conjunction with a server written in Java to provide a DBI front end to a JDBC driver. The Perl module and Java server may be installed on different machines, as long as socket connections are allowed. The Java server portion is multi-threaded and supports multiple simultaneous connections.

This driver currently supports JDBC drivers which implement the JDBC 1.22 interface. JDBC 2.0-compatible drivers are expected to work, but no JDBC 2.0 functionality is explicitly exposed via DBD::JDBC. The $h->jdbc_func method exposes additional JDBC and driver-specific methods. Only Java methods with primitive or String parameters and return types are currently supported in this way.

The expected use for this module is as a DBI interface to databases with JDBC drivers but no DBI drivers. The implementation of this module was originally done for a non-SQL database in order to take advantage of the existing SQL parser in the databases JDBC driver.

The Java classes provided with this module also allow a Java application or servlet to create a JDBC connection and then execute a Perl script which can use that pre-existing JDBC connection via DBI. This particular functionality was implemented in order to allow Perl customizations to a Java servlet-based application. See the example in the example/ directory.

HA-JDBC project is a JDBC driver implementation that provides light-weight, transparent clustering capabilities to groups of homogeneous JDBC- accessed databases.
Main features:
- Supports any database accessible via JDBC.
- High-availability - Database cluster can lose a node without failing the current transaction.
- Improves performance of concurrent read-access by distributing load across individual nodes.
- Support for full JDBC 3.0 (Java 1.4) feature set.
- Compatible with JDBC RowSet implementations found in Java 1.5.
- Out-of-the-box database-independent strategies for synchronizing a failed cluster node.
- Exposes JMX management interface to allow administration of database clusters.
- Open source (LGPL).

StelsDBF is a DBF JDBC type 4 driver that allows to perform SQL queries and other JDBC operations on DBF files (dBase III/ IV/ V, xBase, FoxPro, FoxBase, Clipper).
StelsDBF driver is completely platform-independent and does not require installing additional client or server software to provide access to DBF files. It can be effectively used to create, process and export DBF databases in your Java applications.
Main features:
- It supports most keywords of ANSI SQL92
- It supports inner and outer table joins
- It supports CREATE, INSERT, UPDATE and DELETE statements
- It supports transactions
- It supports aggregate, converting, string and user-defined SQL functions
- It is a platform independent

SQLiteJDBC is a JDBC driver for SQLite which is written as a Java JNI layer over the SQLite 3.3.x API.

SQLiteJDBC supports the most commonly used features of JDBC that can be efficiently implemented on top of SQLite. Only a single native JNI library is required, and SQLite is compiled in.

Binaries are provided for Linux, Mac OS X, and Windows.

HDBC is a Haskell Database Connectivity.

HDBC provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with any number of backend SQL databases (MySQL, Oracle, PostgreSQL, ODBC-compliant databases, etc.)

HDBC is modeled loosely on Perls DBI interface http://search.cpan.org/~timb/DBI/DBI.pm, though it has also been influenced by Pythons DB-API v2, JDBC in Java, and HSQL in Haskell.

HDBC is a from-scratch effort. It is not a reimplementation of HSQL, though its purpose is the same.

aSVERD project is a Scalable Vector Graphics Entity Relationship Diagram generator. It is a tool that should be seen as part of a tool chain rather than a complete solution. What it does is read tables and relationships from a database and generate an SVG file containing the tables and links.
The motivation for creating this was than I have worked in many organisations that have databases with no ERDs and no tools for creating them. I finally got so fed up that I decided to do something about it and this is the result.
The way it is intended to work is that you point SVERD at your database and it creates an SVG file containing all tables and links between them. It DOES NOT attempt to create a fancy layout. it just puts the tables on the diagram in a grid. This can be viewed in a web browser (may need an SVG plug-in). You then use an SVG editor, such as GLIPSGraffiti to lay ou the tables. If you re-run SVERD on an exisitng output file it will not move the tables, therefore the diagram can be updated with out loosing your edits.
NOTE: the links between the tables are rendered using JavaScript, so that if you move the tables around in an editor, the links stay with them. The disadvantage of this is that the editor may not show the links while you are editing (this is the case with GLIPS).
If the table references are not defined in the database they can be supplied in a text file.
Usage
java -jar asverd.jar PropertiesFile
Or
java -jar asverd.jar -d driver -c connectionString -u user -p password [-o outputFile] [-q tableQuery] [-s schema] [-c catalog] [-r refs.txt]
e.g. sverd.TableLister -d com.mysql.jdbc.Driver -c jdbc:mysql://168.0.0.200:3306/DataBase1 -u fred -p secret
The properties file should contain
sverd.driver=databaseDriver
sverd.url=connectionString
sverd.user=username
sverd.password=password
sverd.outputFile=outputFile (optional - STDOUT used if not present)
sverd.tableQuery=query for table name - e.g. INV% (optional - all tables returned if not present)
sverd.schema=database schema (optional - leave out for DBs that do not use)
sverd.catalog=database catalog (optional - leave out for DBs that do not use)
sverd.references=refs.txt (optional - a file containing referecnes if these are not defined in the database. This file should be of the format TABLE [tablename] [foriegnKeyColName] REFERENCES [tablename] [primaryKeyColName] - I know flat text files are not trendy but this format is relatively easy to generate from either XML or SQL (via AWK, SED, PERL, etc)
Enhancements:
- This release fixes bugs with using the SVG in FireFox and adds JavaScript based zooming (click an entity to zoom). The jar contains source and class files

jdbfviewer allows you to display dbf files in a JTable view (and optionally delete rows). Not all versions of dbf are supported. The memo-field isnt tested. No future development is planned.

This is work in progress, without progress.

I created the viewer to view lots of dbf-Files, and did not add any functionality you would probably expect, but which I didnt need.

Later I was asked to add an option to delete rows, which I only started to implement, but without the convenience to select a filename for example.

Another missing feature is, to change values of fields, but I guess its not too much work, to get it done.

jTDS is an open source 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL Server (6.5, 7, 2000 and 2005) and Sybase (10, 11, 12, 15). jTDS is based on FreeTDS and is currently the fastest production-ready JDBC driver for SQL Server and Sybase.
jTDS is 100% JDBC 3.0 compatible, supporting forward-only and scrollable/updateable ResultSets, concurrent (completely independent) Statements and implementing all the DatabaseMetaData and ResultSetMetaData methods.
Quite a few of the commercial JDBC drivers out there are based on jTDS (or FreeTDS), even if they no longer acknowledge this.
jTDS has been tested with virtually all JDBC-based database management tools and is the driver of choice for most of these (recommended for DbVisualizer and SQuirreL SQL, distributed with Aqua Data Studio and DataDino).
jTDS is also becoming a common choice for enterprise-level applications: it passes both the J2EE 1.3 certification and Hibernate test suites, and is recommended for JBoss, Hibernate, Atlassian JIRA and Confluence and Compiere.
jTDS is free software. jTDS is released under the terms of the GNU LGPL, giving you not only the posibility to debug and tweak it to your own liking but also to use it in and distribute it with your free or commercial applications.
The other "free" choices, the JDBC-ODBC bridge and Microsofts own JDBC driver are not actually free. If you encounter an issue with any of them you wont be able to fix it yourself and response times from both Microsoft and Sun are anything but short. Also, both of them lack functionality (the Microsoft driver implements JDBC 2.0, while the bridge is just a JDBC 1.0 implementation) and have serious stability problems: the bridge crashes the JVM if the ODBC driver has any problem and Microsoft just has no intention of really supporting Java/JDBC.
jTDS is also the most performant JDBC driver for both SQL Server and Sybase. We have an older benchmark result but we strongly encourage you to download any benchmark published by commercial JDBC driver vendors and see for yourself. Here are a couple of benchmarks you could use: JNetDirects JDBC Performance Benchmark and i-net Softwares BenchTest 2.1 for MS SQL Server.
Anyway, just give it a spin.
Enhancements:
New features:
- Support for Sybase ASE 15
- Improved support for SQL Server 2005 varchar(max) and varbinary(max)
- Complete handling of cursor exceptions and downgrading
- Better handling of cancels and timeouts
- Configurable socket timeout
- Subclasses of basic JDBC types recognized as setObject() values
Major bug fixes (out of over 30 fixes):
- Statement pool memory leak
- Java 1.5 BigDecimal problems
- Possible synchronization problems
- setAutoCommit() behavior not according to specification
- getTimestamp() returns invalid value after calling getString()
- Cursor opens fails when cursor threshold -1
- iso_1 charset and Sybase
- "All pipe instances are busy" not handled properly
- SSL fails with SQL Server 2005
- Sybase: insert UTF8 string fails when length is 255