Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ASA 8.01 TimeStamp Issue

6 posts in General Discussion Last posting was on 2003-06-11 18:08:03.0Z
Mike Niemann Posted on 2003-06-04 17:12:20.0Z
From: "Mike Niemann" <mniemann@oowidgets.com>
Subject: ASA 8.01 TimeStamp Issue
Date: Wed, 4 Jun 2003 13:12:20 -0400
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <O21Rl1rKDHA.187@forums-2-dub>
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: unknown-167-83-10.baxter.com 167.83.10.24
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1151
Article PK: 3062

It appears that there's a problem with ASA 8 concerning the Timestamp type.
When a Timestamp field is set to "0001-12-25", ASA considers it a valid date
but is unable to differentiate between this date and any other dates.

We have a table being altered. A timestamp field will be part of the Primary
Key. When I search for duplicate records using a select, ASA returns none.
However, when I attempt to create the Primary Key, ASA is unable because of
duplicate records. These are the identified duplicate records:

field1 (Integer) field2 (integer) field3 (timestamp)


1 1 0001-12-15

1 1 0001-03-23

1 1 2001-05-10

Therefore, ASA seems unable to differenciate between these Timestamp values
in some of the cases such as creating a Primary Key or an Index.

Regards, Mike Niemann


Chris Keating (iAnywhere Solutions) Posted on 2003-06-04 17:20:27.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <keating@iAnywhere.com>
References: <O21Rl1rKDHA.187@forums-2-dub>
Subject: Re: ASA 8.01 TimeStamp Issue
Date: Wed, 4 Jun 2003 13:20:27 -0400
Lines: 59
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <eFO6e4rKDHA.311@forums-1-dub>
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: 172.31.140.19
Path: forums-1-dub!forums-master.sybase.com!forums-1-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1152
Article PK: 3397

This is not a channel to report defects to iAnywhere.Within North America,
you can reach Technical Support by calling 1-800-8SYBASE. If you are
located outside of North America, you can find the contact information for
your local Sybase Support Center by going to the Sybase home page at
http://www.sybase.com, clicking on the "Support" link at the top of the
page, and then choosing "Support Centers" from the left hand frame.

You can always report a bug for free by visiting CaseXpress at
http://casexpress.sybase.com/cx/cx.stm. When submitting calls through
CaseXpress, please make sure to give an accurate description of the steps
you take to reproduce the bug, and include any files that may be needed
(database, source code) to reproduce the problem.

--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8
iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use CaseXpress to report bugs http://casexpress.sybase.com

"Mike Niemann" <mniemann@oowidgets.com> wrote in message
news:O21Rl1rKDHA.187@forums-2-dub...
> It appears that there's a problem with ASA 8 concerning the Timestamp
type.
> When a Timestamp field is set to "0001-12-25", ASA considers it a valid
date
> but is unable to differentiate between this date and any other dates.
>
> We have a table being altered. A timestamp field will be part of the
Primary
> Key. When I search for duplicate records using a select, ASA returns none.
> However, when I attempt to create the Primary Key, ASA is unable because
of
> duplicate records. These are the identified duplicate records:
>
> field1 (Integer) field2 (integer) field3 (timestamp)
>
>
> 1 1 0001-12-15
>
> 1 1 0001-03-23
>
> 1 1 2001-05-10
>
> Therefore, ASA seems unable to differenciate between these Timestamp
values
> in some of the cases such as creating a Primary Key or an Index.
>
> Regards, Mike Niemann
>
>
>


Glenn Paulley Posted on 2003-06-04 17:32:44.0Z
Date: Wed, 04 Jun 2003 13:32:44 -0400
From: Glenn Paulley <paulley@ianywhere.com>
Reply-To: paulley@ianywhere.com
Organization: iAnywhere Solutions
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: Re: ASA 8.01 TimeStamp Issue
References: <O21Rl1rKDHA.187@forums-2-dub>
In-Reply-To: <O21Rl1rKDHA.187@forums-2-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <ObNdJBsKDHA.275@forums-2-dub>
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: vpn-dub-194.sybase.com 10.22.120.194
Lines: 44
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1153
Article PK: 3398

This is a known problem that is corrected in ASA versions 8.0.2 and
above. An unload/reload to an 8.0.2 format database is required because
the fix involves a change to how indexes are constructed over timestamp
columns.

Note that it is only date values in the range [0001/1/1, 1600/1/1) that
cause this problem.

Glenn

Mike Niemann wrote:
> It appears that there's a problem with ASA 8 concerning the Timestamp type.
> When a Timestamp field is set to "0001-12-25", ASA considers it a valid date
> but is unable to differentiate between this date and any other dates.
>
> We have a table being altered. A timestamp field will be part of the Primary
> Key. When I search for duplicate records using a select, ASA returns none.
> However, when I attempt to create the Primary Key, ASA is unable because of
> duplicate records. These are the identified duplicate records:
>
> field1 (Integer) field2 (integer) field3 (timestamp)
>
>
> 1 1 0001-12-15
>
> 1 1 0001-03-23
>
> 1 1 2001-05-10
>
> Therefore, ASA seems unable to differenciate between these Timestamp values
> in some of the cases such as creating a Primary Key or an Index.
>
> Regards, Mike Niemann
>
>
>

--
Glenn Paulley
Research and Development Manager, Query Processing
iAnywhere Solutions Engineering

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports: http://casexpress.sybase.com/cx/cx.stm

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer


Mike Niemann Posted on 2003-06-07 00:41:24.0Z
From: Mike Niemann <mniemann@oowidgets.com>
Subject: Re: ASA 8.01 TimeStamp Issue
Date: Fri, 06 Jun 2003 20:41:24 -0400
Organization: OOWidgets
Message-ID: <d3d2evsr4phnkrk3f79e12fg0jcp3fdv59@4ax.com>
References: <O21Rl1rKDHA.187@forums-2-dub> <ObNdJBsKDHA.275@forums-2-dub>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: 24161228hfc85.tampabay.rr.com 24.161.228.85
Lines: 37
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1179
Article PK: 3424

Thank you Glenn, I really appreciate your response.

Regards, Mike Niemann, Baxter Healthcare

On Wed, 04 Jun 2003 13:32:44 -0400, Glenn Paulley

<paulley@ianywhere.com> wrote:

>This is a known problem that is corrected in ASA versions 8.0.2 and
>above. An unload/reload to an 8.0.2 format database is required because
>the fix involves a change to how indexes are constructed over timestamp
>columns.
>
>Note that it is only date values in the range [0001/1/1, 1600/1/1) that
>cause this problem.
>
>Glenn
>
>Mike Niemann wrote:
>> It appears that there's a problem with ASA 8 concerning the Timestamp type.
>> When a Timestamp field is set to "0001-12-25", ASA considers it a valid date
>> but is unable to differentiate between this date and any other dates.
>>
>> We have a table being altered. A timestamp field will be part of the Primary
>> Key. When I search for duplicate records using a select, ASA returns none.
>> However, when I attempt to create the Primary Key, ASA is unable because of
>> duplicate records. These are the identified duplicate records:
>>
>> field1 (Integer) field2 (integer) field3 (timestamp)
>>
>>
>> 1 1 0001-12-15
>>
>> 1 1 0001-03-23
>>
>> 1 1 2001-05-10
>>
>> Therefore, ASA seems unable to differenciate between these Timestamp values
>> in some of the cases such as creating a Primary Key or an Index.
>>
>> Regards, Mike Niemann
>>
>>
>>


Mike Niemann Posted on 2003-06-11 15:29:23.0Z
From: "Mike Niemann" <mniemann@oowidgets.com>
References: <O21Rl1rKDHA.187@forums-2-dub> <ObNdJBsKDHA.275@forums-2-dub>
Subject: Re: ASA 8.01 TimeStamp Issue
Date: Wed, 11 Jun 2003 11:29:23 -0400
Lines: 71
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <uFTz56CMDHA.220@forums-1-dub>
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: unknown-167-83-10.baxter.com 167.83.10.24
Path: forums-1-dub!forums-master.sybase.com!forums-1-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1194
Article PK: 3438

Glenn,

I forgot to ask, is there a recommended workaround for 8.01? We haven't come
up with a good one yet.

Regards, Mike Niemann, Baxter Healthcare

"Glenn Paulley" <paulley@ianywhere.com> wrote in message
news:ObNdJBsKDHA.275@forums-2-dub...
> This is a known problem that is corrected in ASA versions 8.0.2 and
> above. An unload/reload to an 8.0.2 format database is required because
> the fix involves a change to how indexes are constructed over timestamp
> columns.
>
> Note that it is only date values in the range [0001/1/1, 1600/1/1) that
> cause this problem.
>
> Glenn
>
> Mike Niemann wrote:
> > It appears that there's a problem with ASA 8 concerning the Timestamp
type.
> > When a Timestamp field is set to "0001-12-25", ASA considers it a valid
date
> > but is unable to differentiate between this date and any other dates.
> >
> > We have a table being altered. A timestamp field will be part of the
Primary
> > Key. When I search for duplicate records using a select, ASA returns
none.
> > However, when I attempt to create the Primary Key, ASA is unable because
of
> > duplicate records. These are the identified duplicate records:
> >
> > field1 (Integer) field2 (integer) field3 (timestamp)
> >
> >
> > 1 1 0001-12-15
> >
> > 1 1 0001-03-23
> >
> > 1 1 2001-05-10
> >
> > Therefore, ASA seems unable to differenciate between these Timestamp
values
> > in some of the cases such as creating a Primary Key or an Index.
> >
> > Regards, Mike Niemann
> >
> >
> >
>
> --
> Glenn Paulley
> Research and Development Manager, Query Processing
> iAnywhere Solutions Engineering
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports: http://casexpress.sybase.com/cx/cx.stm
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available through the
iAnywhere
> Developer Community at www.ianywhere.com/developer
>


Glenn Paulley Posted on 2003-06-11 18:08:03.0Z
Date: Wed, 11 Jun 2003 14:08:03 -0400
From: Glenn Paulley <paulley@ianywhere.com>
Reply-To: paulley@ianywhere.com
Organization: iAnywhere Solutions
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: Re: ASA 8.01 TimeStamp Issue
References: <O21Rl1rKDHA.187@forums-2-dub> <ObNdJBsKDHA.275@forums-2-dub> <uFTz56CMDHA.220@forums-1-dub>
In-Reply-To: <uFTz56CMDHA.220@forums-1-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <#e8hzTEMDHA.220@forums-1-dub>
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: paulley-xp.sybase.com 172.31.141.96
Lines: 74
Path: forums-1-dub!forums-master.sybase.com!forums-1-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1195
Article PK: 3439

Unfortunately, no. The fix requires both a change to the engine and to
the database version, as the scheme for storing DATE values in an index
was modified to correct the error for dates in that range.

Glenn

Mike Niemann wrote:
> Glenn,
>
> I forgot to ask, is there a recommended workaround for 8.01? We haven't come
> up with a good one yet.
>
> Regards, Mike Niemann, Baxter Healthcare
>
> "Glenn Paulley" <paulley@ianywhere.com> wrote in message
> news:ObNdJBsKDHA.275@forums-2-dub...
>
>>This is a known problem that is corrected in ASA versions 8.0.2 and
>>above. An unload/reload to an 8.0.2 format database is required because
>>the fix involves a change to how indexes are constructed over timestamp
>>columns.
>>
>>Note that it is only date values in the range [0001/1/1, 1600/1/1) that
>>cause this problem.
>>
>>Glenn
>>
>>Mike Niemann wrote:
>>
>>>It appears that there's a problem with ASA 8 concerning the Timestamp
>
> type.
>
>>>When a Timestamp field is set to "0001-12-25", ASA considers it a valid
>
> date
>
>>>but is unable to differentiate between this date and any other dates.
>>>
>>>We have a table being altered. A timestamp field will be part of the
>
> Primary
>
>>>Key. When I search for duplicate records using a select, ASA returns
>
> none.
>
>>>However, when I attempt to create the Primary Key, ASA is unable because
>
> of
>
>>>duplicate records. These are the identified duplicate records:
>>>
>>>field1 (Integer) field2 (integer) field3 (timestamp)
>>>
>>>
>>>1 1 0001-12-15
>>>
>>>1 1 0001-03-23
>>>
>>>1 1 2001-05-10
>>>
>>>Therefore, ASA seems unable to differenciate between these Timestamp
>
> values
>
>>>in some of the cases such as creating a Primary Key or an Index.
>>>
>>>Regards, Mike Niemann
>>>
>>>
>>>
>>
>>--
>>Glenn Paulley
>>Research and Development Manager, Query Processing
>>iAnywhere Solutions Engineering
>>
>>EBF's and Patches: http://downloads.sybase.com
>> choose SQL Anywhere Studio >> change 'time frame' to all
>>
>>To Submit Bug Reports: http://casexpress.sybase.com/cx/cx.stm
>>
>>SQL Anywhere Studio Supported Platforms and Support Status
>>http://my.sybase.com/detail?id=1002288
>>
>>Whitepapers, TechDocs, and bug fixes are all available through the
>
> iAnywhere
>
>>Developer Community at www.ianywhere.com/developer
>>
>
>
>

--
Glenn Paulley
Research and Development Manager, Query Processing
iAnywhere Solutions Engineering

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports: http://casexpress.sybase.com/cx/cx.stm

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer