Free hdbc odbc driver software for linux

HDBC Sqlite3 Driver is the Haskell Sqlite v3 backend driver for HDBC.

Please see HDBC itself for documentation on use. If you dont already
have it, you can browse this documentation at
http://darcs.complete.org/hdbc/doc/index.html.

This package provides one function in module Database.HDBC.Sqlite3:

{- | Connect to an Sqlite version 3 database. The only parameter needed is
the filename of the database to connect to.

All database accessor functions are provided in the main HDBC module. -}
connectSqlite3 :: FilePath -> IO Connection

Semtech Touchscreen Driver is a driver on X for the Semtech Touchscreen as found on the GoBook III manufactured by Itronix.

It comes with a calibration program and has been tested on Linux 2.6.9.

You will need a kernel with the following options compiled.

CONFIG_SERIO_RAW=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y

Next you will need to enable raw PS/2 reporting for the touchscreen. Type in the following command:

echo -n "serio_raw" > /sys/bus/serio/devices/serio1/driver

You should see the following message:

serio_raw: raw access enabled on isa0060/serio2 (serio_raw0, minor 1)

Compiling:

Type the following command to compile the driver:

make

Installing:

Do the following as root to install the driver:

make install

Configuration:

You will need to issue this command every time the computer starts so I suggest you stick somewhere in the initalization scripts.

Add a section in xorg.conf or XF86Config that looks like this:

Section "InputDevice"
Driver "semtech"
Identifier "Semtech Touchscreen"
Option "Device" "/dev/serio_raw0"
Option "DebugLevel" "0"
Option "CalibrateA" "-369046"
Option "CalibrateB" "1114"
Option "CalibrateC" "4893014"
Option "CalibrateD" "-2152"
Option "CalibrateE" "-282719"
Option "CalibrateF" "5331971"
Option "CalibrateDiv" "-359811"
EndSection

Note that the device can also be called /dev/psaux depending on your setup.

Start X and run the touchcal program to calibrate your screen. It will ouput the calibration information

There is also a program called touchcal.pl, it requires the Perl Tk toolkit. The program will write calibration information on your X configuration file.

DBD::ODBC Perl module contains a ODBC Driver for DBI.

SYNOPSIS

use DBI;

$dbh = DBI->connect(dbi:ODBC:DSN, user, password);

Private DBD::ODBC Attributes

odbc_more_results (applies to statement handle only!)
Use this attribute to determine if there are more result sets available. SQL Server supports this feature. Use this as follows:

do { my @row; while (@row = $sth->fetchrow_array()) { # do stuff here } } while ($sth->{odbc_more_results});

Note that with multiple result sets and output parameters (i.e. using bind_param_inout, dont expect output parameters to be bound until ALL result sets have been retrieved.
odbc_ignore_named_placeholders

Use this if you have special needs (such as Oracle triggers, etc) where :new or :name mean something special and are not just place holder names You must then use ? for binding parameters. Example: $dbh->{odbc_ignore_named_placeholders} = 1; $dbh->do("create trigger foo as if :new.x :old.x then ... etc");

Without this, DBD::ODBC will think :new and :old are placeholders for binding and get confused.

odbc_default_bind_type

This value defaults to 0. Older versions of DBD::ODBC assumed that the binding type was 12 (SQL_VARCHAR). Newer versions default to 0, which means that DBD::ODBC will attempt to query the driver via SQLDescribeParam to determine the correct type. If the driver doesnt support SQLDescribeParam, then DBD::ODBC falls back to using SQL_VARCHAR as the default, unless overridden by bind_param()

odbc_force_rebind

This is to handle special cases, especially when using multiple result sets. Set this before execute to "force" DBD::ODBC to re-obtain the result sets number of columns and column types for each execute. Especially useful for calling stored procedures which may return different result sets each execute. The only performance penalty is during execute(), but I didnt want to incur that penalty for all circumstances. It is probably fairly rare that this occurs. This attribute will be automatically set when multiple result sets are triggered. Most people shouldnt have to worry about this.

odbc_async_exec

Allow asynchronous execution of queries. Right now, this causes a spin-loop (with a small "sleep") until the SQL is complete. This is useful, however, if you want the error handling and asynchronous messages (see the err_handler) below. See t/20SQLServer.t for an example of this.

odbc_exec_direct

Force DBD::ODBC to use SQLExecDirect instead of SQLPrepare() then SQLExecute. There are drivers that only support SQLExecDirect and the DBD::ODBC do() override doesnt allow returning result sets. Therefore, the way to do this now is to set the attributed odbc_exec_direct. There are currently two ways to get this: $dbh->prepare($sql, { odbc_exec_direct => 1}); and $dbh->{odbc_exec_direct} = 1; When $dbh->prepare() is called with the attribute "ExecDirect" set to a non-zero value dbd_st_prepare do NOT call SQLPrepare, but set the sth flag odbc_exec_direct to 1.

odbc_err_handler

Allow errors to be handled by the application. A call-back function supplied by the application to handle or ignore messages. If the error handler returns 0, the error is ignored, otherwise the error is passed through the normal DBI error handling structure(s).

This can also be used for procedures under MS SQL Server (Sybase too, probably) to obtain messages from system procedures such as DBCC. Check t/20SQLServer.t and mytest/testerrhandler.pl

The callback function takes three parameters: the SQLState, the ErrorMessage and the native server error.

odbc_SQL_ROWSET_SIZE

Here is the information from the original patch, however, Ive learned since from other sources that this could/has caused SQL Server to "lock up". Please use at your own risk!
SQL_ROWSET_SIZE attribute patch from Andrew Brown > There are only 2 additional lines allowing for the setting of > SQL_ROWSET_SIZE as db handle option. > > The purpose to my madness is simple. SqlServer (7 anyway) by default > supports only one select statement at once (using std ODBC cursors). > According to the SqlServer documentation you can alter the default setting > of > three values to force the use of server cursors - in which case multiple > selects are possible. > > The code change allows for: > $dbh->{SQL_ROWSET_SIZE} = 2; # Any value > 1 > > For this very purpose. > > The setting of SQL_ROWSET_SIZE only affects the extended fetch command as > far as I can work out and thus setting this option shouldnt affect > DBD::ODBC operations directly in any way. > > Andrew >

SQL_DRIVER_ODBC_VER

This, while available via get_info() is captured here. I may get rid of this as I only used it for debugging purposes.
odbc_cursortype (applies to connect only!)

This allows multiple concurrent statements on SQL*Server. In your connect, add { odbc_cursortype => 2 }. If you are using DBI > 1.41, you should also be able to use { odbc_cursortype => DBI::SQL_CURSOR_DYNAMIC } instead. For example:

my $dbh = DBI->connect("dbi:ODBC:$DSN", $user, $pass, { RaiseError => 1, odbc_cursortype => 2});
my $sth = $dbh->prepare("one statement");
my $sth2 = $dbh->prepare("two statement");
$sth->execute;
my @row;
while (@row = $sth->fetchrow_array) {
$sth2->execute($row[0]);
}

See t/20SqlServer.t for an example.

odbc_query_timeout

This allows the end user to set a timeout for queries on the ODBC side. After your connect, add { odbc_query_timeout => 30 } or set on the dbh before executing the statement. The default is 0, no timeout. Note that some drivers may not support this attribute.

See t/20SqlServer.t for an example.

odbc_has_unicode (applies to database handle only)
A read-only attribute signifying whether DBD::ODBC was built with the C macro WITH_UNICODE or not. A value of 1 indicates DBD::ODBC was built with WITH_UNICODE else the value returned is 0.

Building WITH_UNICODE affects columns and parameters which are SQL_C_WCHAR, SQL_WCHAR, SQL_WVARCHAR, and SQL_WLONGVARCHAR.

When odbc_has_unicode is 1, DBD::ODBC will:

bind columns the database declares as wide characters as SQL_Wxxx

This means that UNICODE data stored in these columns will be returned to Perl in UTF-8 and with the UTF8 flag set.
bind parameters the database declares as wide characters as SQL_Wxxx

Parameters bound where the database declares the parameter as being a wide character (or where the parameter type is explicitly set to a wide type - SQL_Wxxx) can be UTF8 in Perl and will be mapped to UTF16 before passing to the driver.
NOTE: You will need at least Perl 5.8.1 to use UNICODE with DBD::ODBC.

NOTE: At this time SQL statements are still treated as native encoding i.e. DBD::ODBC does not call SQLPrepareW with UNICODE strings. If you need a unicode constant in an SQL statement, you have to pass it as parameter or use SQL functions to convert your constant from native encoding to Unicode.

NOTE: Binding of unicode output parameters is coded but untested.

NOTE: When building DBD::ODBC on Windows ($^O eq MSWin32) the WITH_UNICODE macro is automatically added. To disable specify -nou as an argument to Makefile.PL (e.g. nmake Makefile.PL -nou). On non-Windows platforms the WITH_UNICODE macro is not enabled by default and to enable you need to specify the -u argument to Makefile.PL. Please bare in mind that some ODBC drivers do not support SQL_Wxxx columns or parameters.

UNICODE support in ODBC Drivers differs considerably. Please read the README.unicode file for further details.

odbc_version (applies to connect only!)

This was added prior to the move to ODBC 3.x to allow the caller to "force" ODBC 3.0 compatibility. Its probably not as useful now, but it allowed get_info and get_type_info to return correct/updated information that ODBC 2.x didnt permit/provide. Since DBD::ODBC is now 3.x, this can be used to force 2.x behavior via something like: my $dbh = DBI->connect("dbi:ODBC:$DSN", $user, $pass, { odbc_version => 2});

Apache LDAP vhost driver project lets you put vhost with all possible information in an LDAP database for both Apache 1.x and 2.x.

Bug report system

With the new maintainence, there is now also a bug report system at the URL http://bugs.bayour.com/ (project mod_ldap_cfg).

Schemas

A schema called mod_ldap_cfg is used.

Apache config

To setup Apache to use this module, the httpd.conf is used.

MyHD/TL880 Linux Driver is a Linux driver for TL880-based HDTV tuner cards.

This is the development page for the Linux driver for the MyHD and other HDTV tuners based on the TL880 chip.

The driver is in early development stage right now, and we need lots of help testing. If you own any TL880-based card, please download the driver using the Downloads link at the left.

Keep in mind that the driver does not support video capture or playback at this time, but we need as many people as possible to run tests to help the driver move along.

iODBC is a cross-platform Driver Manager that comforms to the Microsoft ODBC 2.x & 3.x and X/Open SQL CLI data access specs.
iODBC Driver Manager and SDK enables the development of database-centric solutions that are both database and platform independent.
What is the ODBC Value Proposition?
The ability to develop applications independent of back-end database engine.
What is iODBC?
iODBC is the acronym for Independent Open DataBase Connectivity, an Open Source platform independent implementation of both the ODBC and X/Open specifications. It is rapidly emerging as the industry standard for developing solutions that are language, platform and database independent.
What is the iODBC Value Proposition?
The ability to develop applications independent of back-end database engine, operating system, and for the most part programming language. Although ODBC and iODBC are both C based Application Programming Interfaces (APIs) there are numerous cross language hooks and bridges from languages such as: C++, Java, Perl, Python, TCL etc.
iODBC has been ported to numerous platforms, including:
Linux (x86, Itanium, Alpha, Mips, and StrongArm), Solaris (Sparc & x86), AIX, HP-UX (PA-RISC & Itanium), Digital UNIX, Dynix, Generic UNIX 5.4, FreeBSD, MacOS 9, MacOS X, DG-UX, and OpenVMS.
This is a great SDK for porting WIN32-based ODBC applications to Linux and other OS platforms.
Enhancements:
- Added support for FileDSN
- Added support for Connection Pooling
- Added check for tracefile size
- Call ODBC 2.x functions in driver if application uses ODBC 2.x only calls
- Fixed problem parsing driver result in SQLSetStmtAttr
- Fixed source code readability
- Fixed bug in overwriting driver name
- Fixed check for /Library/ODBC for Mac OS X
- Fixed prototypes
- Rewrote bootstrap script and configure summary
- Use localtime_r in tracing when available
- Fixed build issues with Mac OS X
- Small code cleanups and fixes

The MDB Tools project is a effort to document the MDB file format used in Microsofts Access database package, and to provide a set of tools and applications to make that data available on other platforms.

Specifically, MDB Tools includes programs to export schema and data to other databases such as MySQL, Oracle, Sybase, PostgreSQL, and others.

Also, included is a SQL engine for performing simple SQL queries. The 0.5 release includes an updated GUI interface (screenshot is available here). A sparse but functional ODBC driver is included as well.

MDB Tools currently has read-only support for Access 97 (Jet 3) and Access 2000/2002 (Jet 4) formats. Access 2000 support is a recent addition and may not be as complete as Jet 3 support.

Write support is currently being worked on and the first cut is expected to be included in the 0.6 release.