Free jdbc software for linux

Claros In Touch is a webmail, address book, calendar, and notebook application. Claros In Touch aims to fulfill the need for a stable, full featured messaging application.
Main features:
- Bayesian Spam protection (no need to do setting on mail server, it is bundled with the webmail)
- Message Filtering (custom filters can be applied to the incoming mail)
- Its is developed using Apache Struts, Apache Commons, Claros Commons, JSP and Servlet technology.
- Folder support on the POP3 protocol. (It simulates the IMAP folders by database)
- No need to do database setup (indeed it supports any JDBC compliant database engine), it comes bundled with a ready to run database engine. (Look: http://www.hsqldb.org)
- It is compatible with any standarts compliant POP3 and SMTP server. (No IMAP)
- Operating system independent. Written with regular JSP and servlets.
- Can send HTML e-mail (DHTML based HTML editor included)
- Fully MIME compatible (can read any HTML e-mail)
- An address book aplication
- An advanced notebook application
- A calendar application, with daily, weekly, monthly views and reminder facilities etc...
Enhancements:
- The UI was improved.
- A preference window was added.
- More languages were added.
- Internet Explorer compatibility problems were fixed.
- POP3 mode was re-engineered. List titles were fixed.
- Attachment handling and the drag-drop system were improved.
- Message headers are now shown correctly.
- Message arrived (sound) notification was added.
- A paging system was introduced.
- Inline HTML messages are now shown correctly.
- A HTML sanitizer was added to prevent hacking.
- An address book was added.
- A chat module was added.
- Performance was improved.
- Less system resources are used.

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.

JDBC SQL Profiler is a quickly hacked tool to do statistics on SELECT queries in order to know where it is most efficient to create indexes.

This small tool, released under an Apache-based license connects to the P6Spy JDBC logger and displays in real time the queries going to the database. It uses an integrated SQL parser to build statistics on the most accessed tables and columns and can generate SQL index creation files.

Other information is also gathered and displayed, such as the request time for a single request, for a class of request, and for all the requests. Sorting may be done on these views to detect database problems efficiently.

This tool can be very useful when you have a big volume of queries that you need to analyze not one by one (meaning that the specific time isnt that much of interest), but rather when you want to know what "group" of queries is taking a lot of time, such as queries on the same tables and columns but with different query values. The integrated SQL parser (built with ANTLR) is used to analyze the incoming SELECT queries.

The Swing GUI was based on Apaches Log4J Chainsaw, but all the bugs are mine. Also contributors are welcome to test, make new suggestions, give their opinion and submit patches.

Need a Type 3 JDBC Driver for MS Access or SQL Server? Think RmiJdbc!
RmiJdbc project is a client/server JDBC Driver that relies on Java RMI.
All JDBC classes (like Connection, ResultSet, etc...) are distributed as RMI objects, so that you can distribute as you like the access to any database supporting the JDBC API.
In fact, RmiJdbc is just a bridge to allow remote access to JDBC drivers.
Why RmiJdbc?
- You develop a client/server application with databases on Windows (NT)? Use RmiJdbc along with the JDBC/ODBC Bridge, your Windows (NT) databases become remotely accessible in Java.
- You implement a JDBC Driver? Just implement the JDBC classes locally, dont bother with remote access!
- You need serializable JDBC classes? Here they are.
Enhancements:
- Add features/limitations/changes here

SmallSQL is the ultimate Java Desktop SQL Database Engine with JDBC 3.0 API.
There are 2 solutions to start with SmallSQL DBMS
1.) From an existing Database
You can convert an existing Database with JDbConverter. This is an open source tool to convert a database from one DBMS to another DBMS via JDBC. You can download it and convert your existing JDBC database.
2.) Create a database with a GUI tool
We does not have such tool but we recommended one of the follow:
JDBC Navigator. This is a free graphical Java tool. After you have download it
Select the menu "Open JDBC Data Source"
Name: Small SQL Database
Driver Class: smallsql.database.SSDriver
URL: jdbc:smallsql
Save and Connect
Open the menu "Connection | SQL Window"
Enter "CREATE DATABASE db1" and execute it with ENTER
Close the Connection
Select the menu "Open JDBC Data Source" and change the URL to
jdbc:smallsql:db1
Save and Connect
SQuirreL SQL Client. This is an open source graphical Java tool. After you have download and install it
Create a new JDBC Driver
Name: Small SQL Database
Example URL: jdbc:smallsql:
Create a new Alias
Name: Small SQL db1
JDBC Driver: Small SQL
URL: jdbc:smallsql
Auto Logon: Yes
Connect to the alias "Small SQL db1"
Change to the tab "SQL"
Enter "CREATE DATABASE db1" and execute it
Close the window
Change the alias
JDBC URL: jdbc:smallsql:db1
Connect to the alias "Small SQL db1"
Configuration:
JDBC Driver class name: smallsql.database.SSDriver
JDBC URL: jdbc:smallsql:< database >
< database > is a absolute or relative directory name
In the Java code for a directory "db1" this look like:
Class.forName( "smallsql.database.SSDriver" );
java.sql.Connection con = java.sql.DriverManager.getConnection( "jdbc:smallsql:db1" );
Enhancements:
- JOIN performance was greatly improved with a new algorithm.
- German and Italian translations of the error messages were added, and it is easy to add more translations.
- Some bugs were fixed.

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

Craftsman Spy is a an open source and free framework for JDBC logging. Craftsman Spy is a JDBC driver implementation.

This logger logs all SQL connection and processings with execution spent time, all the stored procedures with arguments, all the batch processings and the result sets.

No need to modify your application in order to integrate JDBC logging with Craftsman Spy. The application MUST use the craftsman.spy.SpyDriver and MUST be launched with the -Dspy.driver=... system property.

Be carefull this JDBC driver SHOULD not be used in production mode. Use it only in development or pre-production system.

,b>Usage:

Code

The two solutions can be used as the following examples :
System.setProperty("spy.driver","vendor.database.Driver");// or with the -Dspy.driver=vendor.database.Driver JVM option
Class.forName("craftsman.spy.SpyDriver");
Connection c = DriverManager.getConnection("jdbc:database:mydata");
Class.forName("craftsman.spy.SpyDriver");
Connection c = DriverManager.getConnection("jdbc:spy:vendor.database.Driver:database:mydata");

Log configuration

The log4j.properties or log4j.xml configuration file SHOULD contain the following lines :
log4j.category.craftsman.spy=DEBUG, SpyFile
log4j.appender.SpyFile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.SpyFile.DatePattern=.yyyy.MM.dd
log4j.appender.SpyFile.File=spy.log
log4j.appender.SpyFile.layout=org.apache.log4j.PatternLayout
log4j.appender.SpyFile.layout.ConversionPattern=%m%n