Related Posts

• Ingres Ruby Driver and Ruby on Rails Adapter version 1.3.0
• Ruby 1.2.2 released
• PHP Ingres 2.2.1 released

Ingres Ruby Driver:

• Restrict tables() to only return non-system tables
• Add support for Ingres datatypes float4, float8, money, decimal, bigint, and ANSI SQL date/time/timestamp

Ruby on Rails adapter:

• Add support for Ruby on Rails 2.1 Migrations – for more information about ActiveRecord Migrations see – http://wiki.rubyonrails.org/rails/pages/UnderstandingMigrations
• Extend driver support for new data types to Rails
• Improved test results for ActiveRecord unit tests – see http://community.ingres.com/wiki/How_to_test_Ruby_on_Rails_with_Ingres

This new release can be obtained from http://www.ingres.com/downloads/connectivity-resources.php or via one of the following links:

• README
• Windows Pre-Built Driver for Ingres 2.6 & Ingres 2006r2(9.1.x)
• Source (Zip File)
• Source (Compressed Tar File)

Alternatively you can checkout this release from our external source code repository:

svn checkout http://code.ingres.com/ingres/drivers/ruby/tags/ingres-ruby-1.3.0

See http://community.ingres.com/wiki/Connectivity_Drivers_Source_Code for more information on working with our external source repository.

Related Posts

• New Ingres Ruby driver and Rails adapter posted
• Ruby 1.2.2 released
• Ruby for Ingres

• Fix quote() in ingres_adapater.rb to use the class of variable rather than the equivalent Ingres column type.
• Fix segvio in Ingres Ruby driver when fetching char/varchar with data longer than 4074 bytes.

The following files have been added to keep a track of the changes made and the work still to be done:

• CHANGELOG
• TODO.txt

The latest readme.html and driver package (source code) can be downloaded from http://www.ingres.com/downloads/prod-download-drivers.php

Should you wish to provide feedback of any sort you can e-mail me (grant (at) planetingres (dot) org), post to the Ingres Ruby driver forum or to comp.databases.ingres.

Related Posts

• New Ingres Ruby driver and Rails adapter posted
• PHP Ingres 2.2.1 released
• PHP Ingres 2.2.0 released

A consultant for an Ingres client based in the US was asked to develop an Ingres interface for RoR. This he did and as part of the agreement the code was handed over to Ingres Corp. with the intention that it got released after a “once over”. Well the code did get a going over, code specific to the original client’s system had to be removed and earlier this year it was made available on Ingres’s website.

Why am I interested now when I failed to even mention the release of the code? Well it appears I am now assisting in the development of the binding and the RoR adapter. Last week I was in California running through what is needed to get the driver in a more usable state. Here are the edited highlights of what was discussed:

• Clean up the build/install scripts
• Document the code, making use of rdoc tags where possible
• Implement missing data type support; SQL Date/Time, Money, Decimal, Float4/8, Long nvarchar
• Fix up the adapter to get 100% coverage on the active_records unit tests
• Allow multiple connections – only one connection per process allowed at present
• other “stuff”…

The plan is to release as often a possible between changes rather than wait for all pieces to be complete. Ideally this will allow for feedback sooner rather than later. Should you wish to provide feedback of any sort you can e-mail me (grant@planetingres.org), post to the Ingres forums or to comp.databases.ingres.

Related Posts

• New Ingres Ruby driver and Rails adapter posted
• Ingres Ruby Driver and Ruby on Rails Adapter version 1.3.0
• Ingres VectorWise Webinars

Related Posts

• Doing More with Even Less – UK IUA 2009 Conference
• UK IUA – 2009 Call for Papers
• UK Ingres User Association Spring Conference

The IUA is delighted to invite you to the one-day Ingres Users Association
Spring Conference on Wednesday 6th June at De Vere Holborn Bars, London.

You will learn, at first-hand, about the Technical Direction for the Ingres
products, the Evolution of Ingres’ Partner Ecosystem as well as Ingres’
strategy in the Business Intelligence and Performance Management
marketplace.

We have received a very strong response to our call for papers for the
event, so you can chose between twenty sessions across five afternoon
tracks.

As the last event was over-subscribed, you should secure your place NOW by
registering via the www.iua.org.uk.

Please do join us at 09:30 on Wednesday 6th June at De Vere Holborn Bars
when you can meet and talk with the most influential people in the Ingres
community throughout the day and evening.

To attend this FREE event – please register via the online IUA Registration
Form. If you experience any problems registering via the Internet site
please email your RSVP to:

conference at iua dot org dot uk (with the obvious changes to make this a
valid email address).

Roy Hann, on behalf of:
UK IUA

updated: made www.iua.org.uk a link you can follow

Related Posts

• Doing More with Even Less – UK IUA 2009 Conference
• UK IUA – 2009 Call for Papers
• IUA presentation – No speaky the COBOL?

The default binding for ODBC appears to be available from http://www.ch-werner.de/rubyodbc/. Building the binding on Windows (this week I happen to be running windows) went ok. The subsequent tests did not go so well .

The following test fails:

$p = $c.proc("insert into test (id, str) values (?, ?)") {}
$p.call(3, "FOO")
$p[4, "BAR"]

An ODBC trace shows that integers as being passed to Ingres as SQL_VARCHAR. This sort of thing is allowed, if a little disagreable, with MySQL but Ingres does not like it.

If you apply the following patch to odbc.c the tests will complete:

diff -rup ruby-odbc-0.998/odbc.c ruby-odbc-0.998_patched/odbc.c
--- ruby-odbc-0.998/odbc.c      2006-05-21 09:38:30.000000000 +0200
+++ ruby-odbc-0.998_patched/odbc.c      2006-05-26 19:44:47.450091400 +0200
@@ -6151,6 +6151,7 @@ stmt_exec_int(int argc, VALUE *argv, VAL
        if (coldef == 0) {
            switch (ctype) {
            case SQL_C_LONG:
+               stype = SQL_INTEGER;
                coldef = 10;
                break;
            case SQL_C_DOUBLE:

Looking at the rest of the code more changes are needed since the ODBC binding sets the default type to SQL_VARCHAR without correcting for other types. If I get more time next week I will review the rest of the code in this function and post the complete diff.

Some random posts