Re: [Info-Ingres] Upgrading from Ingres 2.6 to Ingres 2006-version9.2

#11

Robert Allely wrote:

Quote:

[...]
Theres various other confusing things that I am seeing eg. At 9.2
Date_gmt('25/3/9') returns 2009_03_24 11:00:00 GMT
But at 2.6 it returns 2009_03_25 00:00:00 GMT. Which does not agree with
the above midnight local time.
Our timezone is GMT+13 at present .

Just making sure: Please run "ingprenv" on the installations and check
the value of the II_TIMEZONE_NAME variable. What is the II_TIMEZONE_NAME
value on the installations? Is it the same?

I definitely see this same time problem/behaviour on 2.6 -- it's not a
stock version, but patched one. It may well be that the stock version
stores ingresdates without time/timezone and the behaviour changed later
in a patch.

Quote:

[...]

--
Regards,
Pauli Borodulin
University of Tampere, Finland

#12

Robert Allely wrote:

Quote:

Hi Pauli

The behaviour of ingres has definitely changed between 2.6 and 9.2
At 2.6 if you insert '25/3/9' into a date field it is stored so that
when retrieved it is midnight local time.
At 9.2 it is stored so that when retrieved it is midnight GMT which is
not midnight local time.

Theres various other confusing things that I am seeing eg. At 9.2
Date_gmt('25/3/9') returns 2009_03_24 11:00:00 GMT
But at 2.6 it returns 2009_03_25 00:00:00 GMT. Which does not agree with
the above midnight local time.
Our timezone is GMT+13 at present .

Confused? I am.
It would be better to avoid using date-only and always specify a
date-time because that's what its being used for.
But we would like to upgrade before making any changes to the apps and
data.

I haven't encountered the problem you are describing, perhaps because I
work mostly in the UK, but I think there's a good chance it will turn
out to be something to do with the timezone setting having got changed,
as another poster suggests.

This really just flags up a fundamental problem with the native Ingres
DATE type though, which is that it allows (even invites) you mix three
different types in one column--which is a subtle and deceptively
harmless-seeming design error.

If you do decide to make changes to permanently fix the problem, it
would probably be worth doing it right. Consider adopting the
appropriate ANSI/ISO type (probably ANSIDATE in this case) which is
designed specifically to avoid this kind of problem.

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [Info-Ingres] Upgrading from Ingres 2.6 to Ingres 2006-version9.2

comp.databases.ingres comp.databases.ingres

Re: [Info-Ingres] Upgrading from Ingres 2.6 to Ingres2006-version9.2 - 03-24-2009 , 02:47 PM

Re: [Info-Ingres] Upgrading from Ingres 2.6 to Ingres2006-version9.2 - 03-25-2009 , 03:25 AM