- Update the unit tests to be more independent
- Add support for the Ingres BOOLEAN type
- Add ingres_fetch_assoc()
- Allow for a 0 offset in all ingres field functions
- Update build scripts for OpenVMS CSWS PHP 2.0
- Fix bug 17556 – Handle errors for non-result returning statements
- Fix bug 16960 – SEGV when fetching the results from a row producing procedure
- Fix bug 16990 – SEGV when executing a database procedure
- Fix bug 17510 – Fix php_ii_set_connect_options so they work as documented
- Fix bug 17302 – _close_statement is unable to free active statements
- Fix bug 17207 – Under certain conditions the driver can SEGV when doing cleaning up
- Fix bug 17198 – Unable to close non-result statements
- Fix bug 17092 – SIGBUS when fetching data on 64-bit Solaris
- IIapi_getDescriptor() should only be called for SELECT statements
- Fix bug 16752 – Send all string values as IIAPI_VCH_TYPE

You can download the source code from http://pecl.php.net/get/ingres or install directly from the command line using the command:

sudo pecl install ingres-2.2.2

Pre-built Windows binaries are available from ESD for PHP 5.1.6, 5.2.13 and 5.3.2. An OpenVMS binary for CSWS PHP 2.0 will be updated today. You can raise questions/problems via the Ingres Community Forums, the project home page or via Service Desk.

Related Posts

• PHP Ingres 2.2.1 released
• PHP Ingres 2.2.0 released
• PHP Ingres 2.1.0 released

Getting web applications to connect to Ingres via Apache on UNIX/Linux can be quite fiddly. Here is a simple guide on the setup steps needed to allow the Ingres PHP, Python and Ruby drivers to work with Apache on RedHat Enterprise Linux, CentOS and Fedora Linux. I’ve also published articles on doing the same for Debian/Ubunutu and Novell SLES/OpenSUSE in the Ingres Community Wiki.

Pre-requisites

It is assumed that you have the following installed:

• Ingres 2006 or newer ( Ingres >= 9.0.4 )
• RedHat Enterprise Linux 5.4, CentOS 5.4 and Fedora Linux 11
  • These steps might apply to earlier releases as well
• Apache 2.2.8
  • The steps here apply to other releases of Apache from 1.3 onwards
  • mod_env – An Apache module which modifies the environment which is passed to CGI scripts and SSI pages

Disabling SELinux

As of writing this Ingres and SELinux do not interact very well. To use Ingres on an SELinux enabled system, SELinux needs to be placed in permissive or disabled modes. To determine the current state of SELinux run the following:

sestatus

sample output:

$ sudo /usr/sbin/sestatus
SELinux status:                 disabled

If the status is enforcing then SELinux must be disabled using the command:

setenforce 0
# or to disable SELinux but log exceptions to policy to /var/log/secure
setenforce Permissive

This will only disable SELinux until the next reboot of the server. To make the change permanent edit /etc/sysconfig/selinux, changing SELINUX to disabled or permissive.

Enabling Ingres for Apache

Any user that connects to Ingres must be a known (defined) user. Specifically a user account must be created within Ingres using CREATE USER .... In the case of web applications served by Apache, Tomcat or whatever, the server process owner is the user that Ingres will initially see. To determine the process owner for Apache execute the following:

ps -fe | grep httpd | grep -v grep

On my system I get the following:

[grant@uksl-grant-rhel64 ~]$ ps -fe | grep httpd | grep -v grep
root      3331     1  0 Apr08 ?        00:00:02 /usr/sbin/httpd
apache   23356  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23357  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23358  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23359  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23360  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23361  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23362  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23363  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd

Which shows two user accounts for Apache. The root account can be ignored since it is a monitor/control process that starts up and shuts down servers as required. The processes run under the apache account will be used to connect to Ingres.

To add apache to Ingres run the following, as the ingres administrator:

sql iidbdb <<EOSQL
create user apache\g
commit\g
\q
EOSQL

You should see something similar to:

ingres@esva-suse:~> sql iidbdb <<EOSQL
> create user apache\g
> commit\g
> \q
> EOSQL
INGRES TERMINAL MONITOR Copyright 2008 Ingres Corporation
Ingres Linux Version II 9.2.0 (a64.lnx/143)NPTL login
Tue Apr 13 23:33:18 2010
continue
* Executing . . .
continue
* Executing . . .
continue
* Ingres Version II 9.2.0 (a64.lnx/143)NPTL logout
Tue Apr 13 23:33:18 2010

Now the Ingres DBMS is setup for the Apache web server.

Enabling Apache for Ingres

1. Edit, (as root), /etc/sysconfig/httpd to include the following:

    II_SYSTEM=/opt/Ingres/IngresII
    LD_LIBRARY_PATH=/opt/Ingres/IngresII/ingres/lib:/opt/Ingres/IngresII/ingres/lib/lp32
    ODBCSYSINI=/opt/Ingres/IngresII/ingres/files
    export II_SYSTEM LD_LIBRARY_PATH ODBCSYSINI

   Note – ODBCSYSINI is only needed for the Python driver or applications based on ODBC

2. Create a new config file (as root), /etc/httpd/conf.d/ingres.conf, adding the following:

PassEnv II_SYSTEM LD_LIBRARY_PATH ODBCSYSINI

3. Restart apache (as root):

   service httpd restart

Verifying the setup

To see that the environment variables are visible the following code snippets can be executed through Apache through PHP and mod_python.

PHP

• Code:

  < ?php
    echo "II_SYSTEM is :" .$_SERVER["II_SYSTEM"] . "<br/>\n";
    echo "LD_LIBRARY_PATH is :" .$_SERVER["LD_LIBRARY_PATH"] . "<br />\n";
  ?>

• Sample Output:

  II_SYSTEM is :/opt/Ingres/IngresII
  LD_LIBRARY_PATH is :/opt/Ingres/IngresII/ingres/lib:/opt/Ingres/IngresII/ingres/lib/lp32
  

Python

• Code, save as python_env.py:

from mod_python import apache
def environment(req):
    req.content_type = "text/html"
    req.add_common_vars()
    env_vars = req.subprocess_env.copy()
    req.write('< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">')
    req.write('<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">')
    req.write('<head><title>mod_python.publisher</title></head>')
    req.write('<body>')
    req.write('<h2>Environment Variables</h2>')
    req.write('<table border="1">')
    req.write('<tr><td>%s</td><td>%s</td></tr>' % ("II_SYSTEM", env_vars['II_SYSTEM']))
    req.write('<tr><td>%s</td><td>%s</td></tr>' % ("LD_LIBRARY_PATH", env_vars['LD_LIBRARY_PATH']))
    req.write('</table>')
    req.write('</body>')
    req.write('</html>')

• Ouput from http://localhost/env.py/environment:

   Environment Variables
   II_SYSTEM	/opt/Ingres/II
   LD_LIBRARY_PATH	/lib:/usr/lib:/usr/local/lib:/opt/Ingres/II/ingres/lib:/opt/Ingres/II/ingres/lib/lp32
  

If you have any comments feel free to post them below.

Updated Apr 14, 2010 9:50 to include SELinux information

Related Posts

• Improving the Improved – docs.ingres.com
• Ingres VectorWise Webinars
• IUA VectorWise Demo Video

Related Posts

• Ingres JDBC Driver available through Maven
• Using Ingres with Grails via a Hibernate DAO
• Logging Ingres JDBC connections under tomcat

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

Recently I found the need to use a DAO data source based on an external library in my application. In fact a different data source from my application against which I needed to connect an Ingres database. First off it sounded quite difficult but in the end it was really easy to do.

The fact that it was Ingres and not another RDBMS such as Oracle or MySQL presented no problems. Not even if it’s going to be the database administration for the application. I’ve come across this sort of situation before and haven’t had any problems apart from some data-type incompatibilities, nothing serious.

It was no problem that I needed to use different data source in my application, Just give the source a different name and that’s it. How and where to install? I edited resources.xml adding the new data source and the bean that references the DAO, like so:

<!--- resources.xml -->
< ?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
    <bean id="dataSourceIngres">
        <property name="driverClassName" value="ca.ingres.jdbc.IngresDriver" />
        <property name="url" value="jdbc:ingres://DATABASE" />
        <property name="username" value="USERNAME" />
        <property name="password" value="PASSWORD" />
    </bean>
    <bean id="ingresDao" factory-method="getInstance">
       <property name="dataSource"><ref local="dataSourceIngres"/></property>
    </bean>
</beans>

After that you call getInstance() for the DAO in the application which in turn calls the corresponding method passing the necessary arguments.

—–

Editor’s note: Fátima is using the driver class ca.ingres.jdbc.IngresDriver and not com.ingres.jdbc.IngresDriver since the client is using Ingres 2.6.

Related Posts

• Maven driver repository updated
• Ingres JDBC Driver available through Maven
• Logging Ingres JDBC connections under tomcat

Related Posts

• PECL ingres-2.2.2 released
• PHP Ingres 2.2.1 released
• PHP 5.3.0 released

For those who don’t know, Maven is a dependency management and project lifecycle tool for Java projects. The hosting of the Ingres JDBC driver in the central repository raises the profile of the Ingres Database and should make it even easier and appealing for new developers to pick up Ingres as their development database.

Alan Raison has written up some notes in our community wiki and in his blog.

I would like to express my thanks for all those who made this possible, especially to Alan who pushed for this in the first place.

Related Posts

• Maven driver repository updated
• Using Ingres with Grails via a Hibernate DAO
• Logging Ingres JDBC connections under tomcat

Related Posts

• PHP Ingres 2.2.0 released
• PHP Ingres 2.1.0 released
• PHP driver 2.0.2 released

Related Posts

• PHP Ingres 2.2.1 released
• PHP Ingres 2.2.0 released
• PHP Ingres 2.1.0 released

This update is implements several bits of new functionality as can seen from the CHANGELOG

• Add ingres.fetch_buffer_size to configure to the number of rows ingres_query() will fetch.
• Add ingres_charset() to fetch the installation II_CHARSETxx value
• Add ingres.describe ini setting to allow disabling of DESCRIBE INPUT if desired
• Add support for DESCRIBE INPUT
• Add ingres_escape_string()
• Add ingres_result_seek() to support row positioning

Some Links:

• Package home – http://pecl.php.net/package/ingres
• Changelog – http://pecl.php.net/package-changelog.php?package=ingres
• Source Download – http://pecl.php.net/get/ingres-2.1.0.tgz
• W32 Download – http://esd.ingres.com/product/drivers/PHP/Windows_32-Bit

Related Posts

• PHP Ingres 2.2.1 released
• PHP Ingres 2.2.0 released
• PHP driver 2.0.2 released