Free odbc driver software for linux

HDBC ODBC Driver is the Haskell ODBC backend driver for HDBC. This driver has been tested on Windows and on Linux with unixODBC. It should also be compatible with iODBC, though this has not been tested. It should be portable to any platform supported by both Haskell and unixODBC.

This driver is the preferred method of communicating with MySQL from Haskell.

MYSQL NOTE

Important note for MySQL users:

Unless you are going to use InnoDB tables, you are strongly encouraged to set

Option = 262144

in your odbc.ini (for Unix users), or to disable transaction support in your DSN setup for Windows users.

If you fail to do this, the MySQL ODBC driver will incorrectly state that it
supports transactions. dbTransactionSupport will incorrectly return True. commit and rollback will then silently fail. This is certainly /NOT/ what you want. It is a bug (or misfeature) in the MySQL driver, not in HDBC.

You should ignore this advice if you are using InnoDB tables.

JDBC Driver for SQLite is a thin layer on top of the SQLite 3.3.x C API. The native JNI library has SQLite compiled into it so all you need to do is include the two files packaged above in your project.
Usage:
Download the binary for the platform you are developing on. Open the tarball and copy the two files into your application directory:
sqlitejdbc.jar
[lib]sqlitejdbc.[dll, so, jnilib]
Reference the driver in your code:
Class.forName("org.sqlite.JDBC");
Connection conn = DriverManager.getConnection("jdbc:sqlite:filename");
// ... use the database ...
conn.close();
And call your program with the drivers JAR file in the classpath and the C library in the librarypath. E.g.
java -cp lib/yourprog.jar:lib/sqlitejdbc.jar
-Djava.library.path=lib
yourprog.Main
Enhancements:
- The driver is now thread-safe and fully supports UTF-16.
- There are binaries for Mac OS, Linux, and Windows, and instructions for compiling with MSVC.

If you want to receive IP over Satellite and DVB on your Linux machine, you might want to buy one of these DVB PCI cards (see also the developer section for a list of card revisions supported by our driver):

* The Siemens DVB card - this is the card we developped the Linux drivers for (thanks to the Siemens guys). The Siemens DVB-S card is identical to the cards built by Hauppauge, Technotrend, Galaxis and Katek. We also support the Siemens DVB-C card.
* Hauppauge has released a low budget version of the Siemens card. The WinTV Nova has no MPEG2 decoder chip anymore. From driver version 0.8 on we support this card - you should be able to get a complete transport stream from it.
* Technotrend has developed a DVB-T card and our driver also supports this card (both, the version with DSP and the Nova card). Most DVB-S cards (except for Version 1.6) are also supported by us. The Technotrend DVB-C card (at least the newer version 2.1) is currently not working with our driver.
* The Telemann Skymedia card - never seen that card, but there are Linux drivers
* The Pentamedia cards - Linux drivers for a IP-over-Satellite card.

uLan Driver provides 9-bit message oriented communication protocol, which is transferred over RS-485 link.
Characters are transferred same way as for RS-232 asynchronous transfer except parity bit, which is used to distinguish between data characters and protocol control information. A physical layer consists of one twisted pair of leads and RS-485 transceivers.
Use of 9-bit character simplifies transfer of binary data and for intelligent controllers can lower the CPU load, because of the CPU need not to care about data characters send to other node. Producers of most microcontrollers for embedded applications know that and have implemented 9-bit extension in UARTs of most of todays MCUs. There is the list below to mention some of them:
- all Intel 8051 and 8096 based MCUs with UART
- members of Motorola 683xx family ( 68332, 68376, ... )
- Hitachi H8 microcontrollers
The driver is implemented as relatively independent layers and subsystems. Messages are prepared and received in the driver dedicated memory. This memory is divided into blocks with uniform size with atomic allocation routines.
When message is being stored into blocks, head of message with couple of data bytes is stored in the first allocated memory block. If all data cannot be stored in the first block, next blocks are allocated and linked together.
The message heads are linked in bidirectional linked lists of messages prepared for sending, processed messages and messages prepared for client notification. These lists or queues are main mechanism for transferring of messages between subsystems.
Link protocol is programmed as finite state automata with state stack, which state routines are executed by interrupt handler. State routine can return positive integer information, negative error notification or zero, which leads to wait for next interrupt. Information or error is used as input parameter when state routine is called.
When the state routine wants initiate transfer to another state routine it changes pointer to the actual state routine. If previous state routine returns nonzero value new routine is called immediately, in other case next interrupt invokes new state routine.
There is stack of callers of actual state routines which enables to constructs automata subsystems, which can be used in more places in main automata loop. Main purpose of this automata is to send or process messages coming in list of messages prepared for sending and if specified, move these messages onto list of messages prepared for client notification.
Received messages are put onto this list too. Subsystem is supervised by timeout handler, which can revitalize communication in case of die of other node. The interrupt and timeout handlers are fully SMP reentrant.
The automata subsystem uses pointers to chip driver routines for hardware port manipulation. This is only part dependent on used chip, today 82510, 16450 and OX16C950PCI. These routines can send and receive 9 bit character, connect to RS-485 line by the arbitration sequence, wait for specified time for character and initialize and close port.
File operation subsystem makes interface between OS kernel VFS and client message queues. It enables to prepare single or multi-frame messages and stores notifications of received or processed messages in clients private state structures. This part is heavily operating system dependent.
Enhancements:
- This release enables you to build the driver within the WDF framework for Windows.
- Updates to support the latest Linux 2.6.x kernels are included (tested to 2.6.19).
- Changes to allow stand-alone system-less build for ARM targets (LPC21xx) are included.
- The OMK has been selected as the default build.
- The "switch2std" script allows you to switch to the old build system.