Free jdbc 0.70 software for linux

JDBC is a Perl 5 interface to Java JDBC (via Inline::Java).

SYNOPSIS

use JDBC;

JDBC->load_driver("org.apache.derby.jdbc.EmbeddedDriver");

my $con = JDBC->getConnection($url, "test", "test");

my $s = $con->createStatement();

$s->executeUpdate("create table foo (foo int, bar varchar(200), primary key (foo))");
$s->executeUpdate("insert into foo (foo, bar) values (42,notthis)");
$s->executeUpdate("insert into foo (foo, bar) values (43,notthat)");

my $rs = $s->executeQuery("select foo, bar from foo");
while ($rs->next) {
my $foo = $rs->getInt(1);
my $bar = $rs->getString(2);
print "row: foo=$foo, bar=$barn";
}

This JDBC module provides an interface to the Java java.sql.* and javax.sql.* JDBC APIs.

When reading a lot of data from disk or network filesystem, e.g. during a backup, buffer cache pollution can be a substantial performance problem for other processes on the machines involved due to buffer cache pollution. odirect is intended to provide a convenient way of avoiding that on systems that offer an O_DIRECT value for open().
odirect provides a C library and SWIG code to make it easy to use from your favorite scripting language.
This project is in the toddler stage:
tests run:
- Ive tested the C library from a C program. This test only reads via odirect
- Ive tested the swig interface code via a python script that uses the swig interface directly. This test too only reads via odirect
- Ive tested the swig interface code via a python wrapper that gives module much more pythonic functionality. This test reads via both odirect and the usual Python file I/O, and compares
- Ive tested the pythonic interface wrapped with bufsock. This test only reads via odirect, but bufsock adds the ability to read sub-block pieces from a buffered full-length block
Caveats:
- Although the tests are pretty good, Ive used this in only one real application so far - and thats my pyindex program
- Ive only tested with C and Python so far, and frankly, Im pretty happy leaving it there for now at least, since my favorite programming languages at this time are C, bash and Python. If youre interested in other languages, please drop me a note - ideal would be diffs for the Makefile and any supporting files, like odirect.whateverExtension wrappers.
- 0.55 had no write support; only read. The current version, 0.65, has 100% untested write support. Thats right - all that testing is only checking reading.
- No "install" rule in the Makefile yet.
- The various python modules insert "." on their python path from too many places; this should be done in the test programs themselves, not the module(s) lest we create (and leave) a security issue
Enhancements:
- This release adds C++ support, bringing the list of supported languages to C, C++, and Python.

JDBCImporter provides a consistent mechanism for importing data from a file to a database, exporting data from a database to a file, and generating data.
JDBCImporter API can run from the command line using an XML config file or from inside an Ant build script. It works with CSV, fixed data, and XML files and supports numbers, strings, and date/times as database column types.
Custom classes can be used to parse different file formats, format column values into different file formats, translate column values before importing or after exporting, or allocate or release JDBC connections.
Installation:
Below are the installation steps for installing JDBC Importer:
unzip the jdbcimporter.zip file
add jdbcimporter.jar and commons-logging.jar to the CLASSPATH.
For example: set CLASSPATH=%CLASSPATH%;INSTALL_DIRlibjdbcimporter.jar;INSTALL_DIRlibcommons-logging.jar
JDBC Importer
Basic Usage:
> java [options] net.sourceforge.jdbcimporter.Importer [plugin file]
where :
config file : the import config file
plugin file : the (optional) property file that describes the plugins available during the import
options : two system properties may be set (both are optional)
jdbcimporter.engine = The import engine to use
jdbcimporter.failonerror = Flag indicating that the import should end if an error occurrs
Enhancements:
- This release fixes a bug with CSV delimiter parser.

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

Blackbox is that fast, light window manager you have been looking for without all those annoying library dependancies.
If you have a C++ compiler and the X Window System you can compile and use it.
Enhancements:
- fix compilation on OpenBSD and Mac OS X
- documentation updates to data/README.menu
- fix bt::Timer to make sure it still works after daylight-savings changes
- fix horizontal text alignment by adding a small indent to all text
- fix sunken gradient rendering: the colors are no longer inverted, and the correct bevel is drawn
- add bt::XDG::BaseDir, which is an implementation of the freedesktop.org basedir-spec version 0.6
- make bt::Pen able to recover from cache faults
- silence messages from bt::PixmapCache about the cache maximum being exceeded
- add bt::Rect::inside(), which ensures that one rectangle is inside the other
- fix bt::Resource to do nothing if filename arguments are empty
- fix bt::Resource::merge() to stop overriding existing entries (it should only add new ones)
- add bt::Texture::textureResource() overload that returns a default texture if the resource cannot be found
- add bt::dirname(), which returns the directory part of a file path
- add bt::mkdirhier(), which is equivalent to mkdir -m mode -p path
- add bt::tolower(), which returns a string with all characters lowercase
- add the "Center Placement" window placement policy, which places all new windows in the center of the screen
- add "Shade Window with Mouse Wheel" and "Toolbar Actions with Mouse Wheel" configuration options
- add window-to-window snapping support. This feature is off by default, you need to set session.windowSnapThreshold to a positive number in your ~/.blackboxrc.
- add support for piped menus. The output of a command can be used to create the blackbox menu. This is done by prepending the pipe character, |, to session.menuFile in ~/.blackboxrc or to [include] filenames.
- [nop] menu entries are now drawn disabled
- fix "Focus Last Window on Workspace" behavior to stop preferring windows that occupy all workspaces
- window placement takes windows with Desktop and Dialog types into consideration and does the appropriate thing (instead of placing them normally)
- remove 1 pixel gaps between windows when doing smart placement
- allow users to override the styles rootCommand in their ~/.blackboxrc
- fix default colors used by blackbox when no style is found
- allow the Toolbar to be raised and lowered with Alt+LeftMouseButton and Alt+MiddleMouseButton, respectively
- fix maximized+shaded windows from disappearing when restarting blackbox
- each windows windowmenu can be accessed now with Mod4+RightMouseButton
- fix fullscreen support to ignore aspect ratios set by applications (specifically, this should fix movie players that are currently displaying 16:9 video on a 4:3 screen)
- fix support for _NET_MOVERESIZE_WINDOW, normally sent from pagers
- fix focus problems caused by applications that try to fake fullscreen by setting focus to an override-redirect window (e.g. rdekstop)

Sepia is a simple Emacs-Perl Interface.

@compls = completions($string [, $type])

Find a list of completions for $string with glob type $type. Completion operates on word subparts separated by [:_], so e.g. "S:m_w" completes to "Sepia::my_walksymtable".

@locs = location(@names)

Return a list of [file, line, name] triples, one for each function name in @names.

@matches = apropos($name [, $is_regex])

Search for function $name, either in all packages or, if $name is qualified, only in one package. If $is_regex is true, the non-package part of $name is a regular expression.

@names = mod_subs($pack)

Find subs in package $pack.

@decls = mod_decls($pack)

Generate a list of declarations for all subroutines in package $pack.

$info = module_info($module, $type)

Emacs-called function to get module information.

$file = mod_file($mod)

Find the likely file owner for module $mod.

@mods = package_list

Gather a list of all distributions on the system. XXX UNUSED

@mods = module_list

Gather a list of all packages (.pm files, really) installed on the system, grouped by distribution. XXX UNUSED

@mods = doc_list

Gather a list of all documented packages (.?pm files, really) installed on the system, grouped by distribution. XXX UNUSED

lexicals($subname)

Return a list of $subnames lexical variables. Note that this includes all nested scopes -- I dont know if or how Perl distinguishes inner blocks.

$lisp = tolisp($perl)

Convert a Perl scalar to some ELisp equivalent.

printer(@res [, $iseval])

Print @res appropriately on the current filehandle. If $iseval is true, use terse format. Otherwise, use human-readable format.

repl(*FH)

Execute a command interpreter on FH. The prompt has a few bells and whistles, including:

* Obviously-incomplete lines are treated as multiline input.

* C< die > is overridden to enter a recursive interpreter at the point
C< die > is called. From within this interpreter, you can examine a
backtrace by calling "bt", return from C< die > with "r EXPR", or
go ahead and die by pressing Control-c.

Behavior is controlled in part through the following package-globals:

$PS1 -- the default prompt

$STOPDIE -- true to enter the inspector on die()

$STOPWARN -- true to enter the inspector on warn()

%REPL -- maps shortcut names to handlers

$PACKAGE -- evaluation package

$WANTARRAY -- evaluation context

$PRINTER -- result printer (default: print_dumper)

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.