[Info-Ingres] iicolumns query isnt 100% truthful

[Martin Bowes]

Hi All.

 

Here's an interesting thing I've just come across….

 

On an Ingres2006R2 installation I do: select distinct column_datatype from iicolumns

 

It lists all the column datatypes and of course things like 'INGRESDATE'.

 

Now from an Ingres II2.6 installation which uses a vnode to connect to exactly the same database, I run the same query and find all the INGRESDATE stuff has been massaged to simply DATE.

 

All the ansidate stuff (and timestamps, intervals etc) come out exactly as-is on the vnode query.

 

Why has it bothered to massage INGRESDATE to DATE?

 

I assume this is to allow a copydb run on an II2.6 site to have a chance of functioning on a vnode to an 2006R2 site. But when I try that I get an error: E_US0B5A line 1, There is no such function as 'iimacaccess'.

 

Martin Bowes

[Laframboise, André]

Hi Marty,

 

That sounds about right. Probably to create valid copy.in files in a 2.6 environment.

 

A copydb from 2.6 to Ingres 2006 (via a vnode) will create a copy.in with the DATE datatype.

Where the same copydb from Ingres2006 will create the same copy.in with the INGRESDATE datatype.

---

From: info-ingr...@kettleriverconsulting.com [mailto:info-ingr...@kettleriverconsulting.com] On Behalf Of Martin Bowes
Sent: December 3, 2008 10:01 AM
To: Ingres and related product discussion forum
Subject: [Info-Ingres] iicolumns query isnt 100% truthful