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.0.3 "conflict" acting as a reserved word

10 posts in General Discussion Last posting was on 2004-10-04 13:15:43.0Z
Mike Niemann Posted on 2004-09-30 19:56:12.0Z
From: "Mike Niemann" <mniemann@oowidgets.com>
Newsgroups: ianywhere.public.general
Subject: ASA 8.0.3 "conflict" acting as a reserved word
Lines: 13
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Original-NNTP-Posting-Host: 167.83.10.24
Message-ID: <415c64d8$1@forums-2-dub>
X-Original-Trace: 30 Sep 2004 12:56:08 -0700, 167.83.10.24
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 30 Sep 2004 12:56:09 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 30 Sep 2004 12:56:12 -0700
X-Trace: forums-1-dub 1096574172 10.22.108.75 (30 Sep 2004 12:56:12 -0700)
X-Original-Trace: 30 Sep 2004 12:56:12 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3658
Article PK: 7562

We used a variable named "conflict" in one of our triggers... and when we
migrated from 8.0.1 to 8.0.3, the trigger fails because the variable named
"conflict" is now acting as a reserved word.

I have the "reserved word" list for 9.0.1, and "conflict" is not a reserved
word in it either.

Although it might be somewhat unusual <g> to name a varable "conflict"... it
seems we did.

Regards, Mike Niemann


anil k goel Posted on 2004-09-30 20:03:55.0Z
From: "anil k goel" <firstname.no-junk.lastname@spam.ianywhere.com>
Newsgroups: ianywhere.public.general
References: <415c64d8$1@forums-2-dub>
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Lines: 36
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-Original-NNTP-Posting-Host: anilgoel-pc.sybase.com
Message-ID: <415c66a5@forums-2-dub>
X-Original-Trace: 30 Sep 2004 13:03:49 -0700, anilgoel-pc.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 30 Sep 2004 13:03:52 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 30 Sep 2004 13:03:55 -0700
X-Trace: forums-1-dub 1096574635 10.22.108.75 (30 Sep 2004 13:03:55 -0700)
X-Original-Trace: 30 Sep 2004 13:03:55 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3659
Article PK: 7558

It does appear that conflict is indeed a keyword now and the docs need
updating. Your options are:

1. Rename the variable
2. Enclose the variable name in double quotes ( "conflict" )
3. Use the NON_KEYWORDS option

--
-anil
Research and Development, Query Processing
iAnywhere Solutions Engineering

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

"Mike Niemann" <mniemann@oowidgets.com> wrote in message
news:415c64d8$1@forums-2-dub...
> We used a variable named "conflict" in one of our triggers... and when we
> migrated from 8.0.1 to 8.0.3, the trigger fails because the variable named
> "conflict" is now acting as a reserved word.
>
> I have the "reserved word" list for 9.0.1, and "conflict" is not a
> reserved
> word in it either.
>
> Although it might be somewhat unusual <g> to name a varable "conflict"...
> it
> seems we did.
>
> Regards, Mike Niemann
>
>


Mike Niemann Posted on 2004-10-01 00:04:25.0Z
From: Mike Niemann <mniemann@oowidgets.com>
Newsgroups: ianywhere.public.general
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Organization: OOWidgets
Message-ID: <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com>
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 24161228hfc85.tampabay.rr.com
X-Original-NNTP-Posting-Host: 24161228hfc85.tampabay.rr.com
Date: 30 Sep 2004 17:04:25 -0700
X-Trace: forums-1-dub 1096589065 24.161.228.85 (30 Sep 2004 17:04:25 -0700)
X-Original-Trace: 30 Sep 2004 17:04:25 -0700, 24161228hfc85.tampabay.rr.com
Lines: 17
X-Authenticated-User: pbtenbeta
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3664
Article PK: 7563

On 30 Sep 2004 13:03:55 -0700, "anil k goel"

<firstname.no-junk.lastname@spam.ianywhere.com> wrote:

>It does appear that conflict is indeed a keyword now and the docs need
>updating. Your options are:
>
>1. Rename the variable
>2. Enclose the variable name in double quotes ( "conflict" )
>3. Use the NON_KEYWORDS option

Anil,

Thank you for the confirmation... unfortunately this caused a regression
bug for us. We have renamed the variable, but now we have to figure out
how to fix the problem in the field.

Regards, Mike Niemann


anil k goel Posted on 2004-10-01 12:27:38.0Z
From: "anil k goel" <firstname.no-junk.lastname@spam.ianywhere.com>
Newsgroups: ianywhere.public.general
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub> <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com>
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: anilgoel-pc.sybase.com
X-Original-NNTP-Posting-Host: anilgoel-pc.sybase.com
Message-ID: <415d4d3a@forums-1-dub>
Date: 1 Oct 2004 05:27:38 -0700
X-Trace: forums-1-dub 1096633658 10.25.107.153 (1 Oct 2004 05:27:38 -0700)
X-Original-Trace: 1 Oct 2004 05:27:38 -0700, anilgoel-pc.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3667
Article PK: 7566

Mike,

I fully understand your dilemma. I just wanted to add that we are usually
very conservative about introducing new keywords to the grammar and add one
when absolutely necessary. Unfortunately, it is sometimes unavoidable as
more features are added to the language for various reasons (customer
requests, compatibility with other vendors, ANSI standards evolution and so
on).

We continuously talk about finding means of avoiding or minimizing pain for
existing customers when a new keyword is added. Unfortunately, we currently
don't have solutions better than what I outlined below.

We are, as always, willing to consider any suggestions.

--
-anil
Research and Development, Query Processing
iAnywhere Solutions Engineering

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

"Mike Niemann" <mniemann@oowidgets.com> wrote in message
news:8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com...
> On 30 Sep 2004 13:03:55 -0700, "anil k goel"
> <firstname.no-junk.lastname@spam.ianywhere.com> wrote:
>
>>It does appear that conflict is indeed a keyword now and the docs need
>>updating. Your options are:
>>
>>1. Rename the variable
>>2. Enclose the variable name in double quotes ( "conflict" )
>>3. Use the NON_KEYWORDS option
>
> Anil,
>
> Thank you for the confirmation... unfortunately this caused a regression
> bug for us. We have renamed the variable, but now we have to figure out
> how to fix the problem in the field.
>
> Regards, Mike Niemann


Mike Niemann Posted on 2004-10-01 13:32:06.0Z
From: "Mike Niemann" <mniemann@oowidgets.com>
Newsgroups: ianywhere.public.general
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub> <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com> <415d4d3a@forums-1-dub>
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Lines: 65
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: 167.83.10.24
X-Original-NNTP-Posting-Host: 167.83.10.24
Message-ID: <415d5c56@forums-1-dub>
Date: 1 Oct 2004 06:32:06 -0700
X-Trace: forums-1-dub 1096637526 167.83.10.24 (1 Oct 2004 06:32:06 -0700)
X-Original-Trace: 1 Oct 2004 06:32:06 -0700, 167.83.10.24
X-Authenticated-User: pbtenbeta
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3669
Article PK: 7568

Anil,

I appreciate your response, and what you said I can agree with totally.

However, "conflict" is a stealth reserved word... not documented for any
version of ASA. When was it introduced? What is the syntax for using it?
Where was the notice? [especially in view of the regression difficulties
iAnywhere is well aware of]

Regards, Mike Niemann

"anil k goel" <firstname.no-junk.lastname@spam.ianywhere.com> wrote in
message news:415d4d3a@forums-1-dub...
> Mike,
>
> I fully understand your dilemma. I just wanted to add that we are usually
> very conservative about introducing new keywords to the grammar and add
one
> when absolutely necessary. Unfortunately, it is sometimes unavoidable as
> more features are added to the language for various reasons (customer
> requests, compatibility with other vendors, ANSI standards evolution and
so
> on).
>
> We continuously talk about finding means of avoiding or minimizing pain
for
> existing customers when a new keyword is added. Unfortunately, we
currently
> don't have solutions better than what I outlined below.
>
> We are, as always, willing to consider any suggestions.
>
> --
> -anil
> Research and Development, Query Processing
> iAnywhere Solutions Engineering
>
> -------------------------------------------------------------------------
> ** Whitepapers, TechDocs, bug fixes are all available through the **
> ** iAnywhere Developer Community at http://www.ianywhere.com/developer **
> -------------------------------------------------------------------------
>
> "Mike Niemann" <mniemann@oowidgets.com> wrote in message
> news:8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com...
> > On 30 Sep 2004 13:03:55 -0700, "anil k goel"
> > <firstname.no-junk.lastname@spam.ianywhere.com> wrote:
> >
> >>It does appear that conflict is indeed a keyword now and the docs need
> >>updating. Your options are:
> >>
> >>1. Rename the variable
> >>2. Enclose the variable name in double quotes ( "conflict" )
> >>3. Use the NON_KEYWORDS option
> >
> > Anil,
> >
> > Thank you for the confirmation... unfortunately this caused a regression
> > bug for us. We have renamed the variable, but now we have to figure out
> > how to fix the problem in the field.
> >
> > Regards, Mike Niemann
>
>


anil k goel Posted on 2004-10-01 13:48:12.0Z
From: "anil k goel" <firstname.no-junk.lastname@spam.ianywhere.com>
Newsgroups: ianywhere.public.general
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub> <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com> <415d4d3a@forums-1-dub> <415d5c56@forums-1-dub>
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Lines: 107
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-Original-NNTP-Posting-Host: anilgoel-pc.sybase.com
Message-ID: <415d6018$1@forums-2-dub>
X-Original-Trace: 1 Oct 2004 06:48:08 -0700, anilgoel-pc.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 1 Oct 2004 06:48:09 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 1 Oct 2004 06:48:12 -0700
X-Trace: forums-1-dub 1096638492 10.22.108.75 (1 Oct 2004 06:48:12 -0700)
X-Original-Trace: 1 Oct 2004 06:48:12 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3670
Article PK: 7572

Mike,

It appears that the keyword was introduced on Mar 8, 2004. Here is the
relevant information that should have been documented (I will try to find
where it was documented).

=================

Versions affected: Jasper, 9.0.2, 8.0.3 (4942)

Customer/Documentation Description:

The conflict() function can be used in conflict resolution triggers to
determine if a particular column is a source of conflict for an UPDATE being
performed on the consolidated database. The parameter to the function is an
identifier which represents a column in the table on which the trigger is
defined. The function returns TRUE if the column appears in the VERIFY list
for an UPDATE statement executed by DBREMOTE and the value provided in the
VALUES list of that statement does not match the original value of the
column in the row being updated; otherwise, the function returns FALSE.

Behavior changes:

"conflict" is now a reserved word.

===============

--
-anil
Research and Development, Query Processing
iAnywhere Solutions Engineering

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

"Mike Niemann" <mniemann@oowidgets.com> wrote in message
news:415d5c56@forums-1-dub...
> Anil,
>
> I appreciate your response, and what you said I can agree with totally.
>
> However, "conflict" is a stealth reserved word... not documented for any
> version of ASA. When was it introduced? What is the syntax for using it?
> Where was the notice? [especially in view of the regression difficulties
> iAnywhere is well aware of]
>
> Regards, Mike Niemann
>
> "anil k goel" <firstname.no-junk.lastname@spam.ianywhere.com> wrote in
> message news:415d4d3a@forums-1-dub...
>> Mike,
>>
>> I fully understand your dilemma. I just wanted to add that we are usually
>> very conservative about introducing new keywords to the grammar and add
> one
>> when absolutely necessary. Unfortunately, it is sometimes unavoidable as
>> more features are added to the language for various reasons (customer
>> requests, compatibility with other vendors, ANSI standards evolution and
> so
>> on).
>>
>> We continuously talk about finding means of avoiding or minimizing pain
> for
>> existing customers when a new keyword is added. Unfortunately, we
> currently
>> don't have solutions better than what I outlined below.
>>
>> We are, as always, willing to consider any suggestions.
>>
>> --
>> -anil
>> Research and Development, Query Processing
>> iAnywhere Solutions Engineering
>>
>> -------------------------------------------------------------------------
>> ** Whitepapers, TechDocs, bug fixes are all available through the **
>> ** iAnywhere Developer Community at http://www.ianywhere.com/developer **
>> -------------------------------------------------------------------------
>>
>> "Mike Niemann" <mniemann@oowidgets.com> wrote in message
>> news:8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com...
>> > On 30 Sep 2004 13:03:55 -0700, "anil k goel"
>> > <firstname.no-junk.lastname@spam.ianywhere.com> wrote:
>> >
>> >>It does appear that conflict is indeed a keyword now and the docs need
>> >>updating. Your options are:
>> >>
>> >>1. Rename the variable
>> >>2. Enclose the variable name in double quotes ( "conflict" )
>> >>3. Use the NON_KEYWORDS option
>> >
>> > Anil,
>> >
>> > Thank you for the confirmation... unfortunately this caused a
>> > regression
>> > bug for us. We have renamed the variable, but now we have to figure out
>> > how to fix the problem in the field.
>> >
>> > Regards, Mike Niemann
>>
>>
>
>


Tom Slee Posted on 2004-10-01 15:25:16.0Z
Message-ID: <415D76DA.1010109@sybase.com>
From: Tom Slee <tom.slee@sybase.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub> <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com> <415d4d3a@forums-1-dub> <415d5c56@forums-1-dub> <415d6018$1@forums-2-dub>
In-Reply-To: <415d6018$1@forums-2-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: tslee-pc2.sybase.com
X-Original-Trace: 1 Oct 2004 08:25:14 -0700, tslee-pc2.sybase.com
Lines: 34
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 1 Oct 2004 08:25:15 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 1 Oct 2004 08:25:16 -0700
X-Trace: forums-1-dub 1096644316 10.22.108.75 (1 Oct 2004 08:25:16 -0700)
X-Original-Trace: 1 Oct 2004 08:25:16 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3673
Article PK: 7575

This feature was missed in the 8.0.3 documentation update. It will be
described in the 9.0.2 documentation when that release goes out.

Tom Slee
iAnywhere Documentation

anil k goel wrote:
> Mike,
>
> It appears that the keyword was introduced on Mar 8, 2004. Here is the
> relevant information that should have been documented (I will try to find
> where it was documented).
>
> =================
>
> Versions affected: Jasper, 9.0.2, 8.0.3 (4942)
>
> Customer/Documentation Description:
>
> The conflict() function can be used in conflict resolution triggers to
> determine if a particular column is a source of conflict for an UPDATE being
> performed on the consolidated database. The parameter to the function is an
> identifier which represents a column in the table on which the trigger is
> defined. The function returns TRUE if the column appears in the VERIFY list
> for an UPDATE statement executed by DBREMOTE and the value provided in the
> VALUES list of that statement does not match the original value of the
> column in the row being updated; otherwise, the function returns FALSE.
>
> Behavior changes:
>
> "conflict" is now a reserved word.
>
> ===============
>


Breck Carter [TeamSybase] Posted on 2004-10-03 17:18:30.0Z
From: "Breck Carter [TeamSybase]" <NOSPAM__bcarter@risingroad.com>
Newsgroups: ianywhere.public.general
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__bcarter@risingroad.com
Message-ID: <c2d0m01ccj8up0pn59mu9gna5ffke5s3cn@4ax.com>
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub> <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com> <415d4d3a@forums-1-dub> <415d5c56@forums-1-dub> <415d6018$1@forums-2-dub> <415D76DA.1010109@sybase.com>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: 64.7.134.118
X-Original-Trace: 3 Oct 2004 10:18:26 -0700, 64.7.134.118
Lines: 47
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 3 Oct 2004 10:18:27 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 3 Oct 2004 10:18:30 -0700
X-Trace: forums-1-dub 1096823910 10.22.108.75 (3 Oct 2004 10:18:30 -0700)
X-Original-Trace: 3 Oct 2004 10:18:30 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3684
Article PK: 7585

Is it a dbremote-only feature, or will it Help MobiLink?

Breck

On 1 Oct 2004 08:25:16 -0700, Tom Slee <tom.slee@sybase.com> wrote:

>This feature was missed in the 8.0.3 documentation update. It will be
>described in the 9.0.2 documentation when that release goes out.
>
>Tom Slee
>iAnywhere Documentation
>
>anil k goel wrote:
>> Mike,
>>
>> It appears that the keyword was introduced on Mar 8, 2004. Here is the
>> relevant information that should have been documented (I will try to find
>> where it was documented).
>>
>> =================
>>
>> Versions affected: Jasper, 9.0.2, 8.0.3 (4942)
>>
>> Customer/Documentation Description:
>>
>> The conflict() function can be used in conflict resolution triggers to
>> determine if a particular column is a source of conflict for an UPDATE being
>> performed on the consolidated database. The parameter to the function is an
>> identifier which represents a column in the table on which the trigger is
>> defined. The function returns TRUE if the column appears in the VERIFY list
>> for an UPDATE statement executed by DBREMOTE and the value provided in the
>> VALUES list of that statement does not match the original value of the
>> column in the row being updated; otherwise, the function returns FALSE.
>>
>> Behavior changes:
>>
>> "conflict" is now a reserved word.
>>
>> ===============
>>

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/ASIN/1556225067/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com


Reg Domaratzki (iAnywhere Solutions) Posted on 2004-10-04 13:15:43.0Z
From: "Reg Domaratzki \(iAnywhere Solutions\)" <Spam_bad_rdomarat@ianywhere.com>
Newsgroups: ianywhere.public.general
References: <415c64d8$1@forums-2-dub> <415c66a5@forums-2-dub> <8i7pl0pjoqh0nq4sm2u9bri8oh241fan5d@4ax.com> <415d4d3a@forums-1-dub> <415d5c56@forums-1-dub> <415d6018$1@forums-2-dub> <415D76DA.1010109@sybase.com> <c2d0m01ccj8up0pn59mu9gna5ffke5s3cn@4ax.com>
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
Lines: 72
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Original-NNTP-Posting-Host: rdomarat-pc.sybase.com
Message-ID: <41614cf5@forums-2-dub>
X-Original-Trace: 4 Oct 2004 06:15:33 -0700, rdomarat-pc.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 4 Oct 2004 06:15:36 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 4 Oct 2004 06:15:43 -0700
X-Trace: forums-1-dub 1096895743 10.22.108.75 (4 Oct 2004 06:15:43 -0700)
X-Original-Trace: 4 Oct 2004 06:15:43 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3688
Article PK: 7588

It's only useable in a RESOLVE CONFLICT trigger, so it's only useable for
SQL Remote.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Breck Carter [TeamSybase]" <NOSPAM__bcarter@risingroad.com> wrote in
message news:c2d0m01ccj8up0pn59mu9gna5ffke5s3cn@4ax.com...
> Is it a dbremote-only feature, or will it Help MobiLink?
>
> Breck
>
> On 1 Oct 2004 08:25:16 -0700, Tom Slee <tom.slee@sybase.com> wrote:
>
> >This feature was missed in the 8.0.3 documentation update. It will be
> >described in the 9.0.2 documentation when that release goes out.
> >
> >Tom Slee
> >iAnywhere Documentation
> >
> >anil k goel wrote:
> >> Mike,
> >>
> >> It appears that the keyword was introduced on Mar 8, 2004. Here is the
> >> relevant information that should have been documented (I will try to
find
> >> where it was documented).
> >>
> >> =================
> >>
> >> Versions affected: Jasper, 9.0.2, 8.0.3 (4942)
> >>
> >> Customer/Documentation Description:
> >>
> >> The conflict() function can be used in conflict resolution triggers to
> >> determine if a particular column is a source of conflict for an UPDATE
being
> >> performed on the consolidated database. The parameter to the function
is an
> >> identifier which represents a column in the table on which the trigger
is
> >> defined. The function returns TRUE if the column appears in the VERIFY
list
> >> for an UPDATE statement executed by DBREMOTE and the value provided in
the
> >> VALUES list of that statement does not match the original value of the
> >> column in the row being updated; otherwise, the function returns FALSE.
> >>
> >> Behavior changes:
> >>
> >> "conflict" is now a reserved word.
> >>
> >> ===============
> >>
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
http://www.amazon.com/exec/obidos/ASIN/1556225067/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com


Greg Fenton Posted on 2004-10-01 17:02:32.0Z
From: Greg Fenton <greg.fenton_NOSPAM_@ianywhere.com>
Organization: iAnywhere Solutions Inc.
User-Agent: Mozilla Thunderbird 1.6.3.2f (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: ASA 8.0.3 "conflict" acting as a reserved word
References: <415c64d8$1@forums-2-dub>
In-Reply-To: <415c64d8$1@forums-2-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: gfenton-t30.sybase.com
Message-ID: <415d8da4$1@forums-2-dub>
X-Original-Trace: 1 Oct 2004 10:02:28 -0700, gfenton-t30.sybase.com
Lines: 20
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 1 Oct 2004 10:02:29 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 1 Oct 2004 10:02:32 -0700
X-Trace: forums-1-dub 1096650152 10.22.108.75 (1 Oct 2004 10:02:32 -0700)
X-Original-Trace: 1 Oct 2004 10:02:32 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3679
Article PK: 7579


Mike Niemann wrote:
> We used a variable named "conflict" in one of our triggers...
>

FYI, our team advocates prepending variable names with an '@' symbol so
that you are guaranteed of it not colliding with reserved words.

This also avoids ambiguity should we come across a table or column which
also has the same name:

UPDATE foo SET conflict = @conflict

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/