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.

trigger change that might affect your applications

5 posts in Trigger Last posting was on 2006-04-01 08:04:43.0Z
Jeremy Mullin Posted on 2006-03-28 23:45:43.0Z
Date: Tue, 28 Mar 2006 23:45:43 +0000 (UTC)
Message-ID: <886edc1510c9f8c8209e3085a5cc@devzone.advantagedatabase.com>
From: Jeremy Mullin <no@email.com>
Subject: trigger change that might affect your applications
Newsgroups: Advantage.Trigger
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-Newsreader: JetBrains Omea Reader 928.2
NNTP-Posting-Host: 198.102.102.44
X-Trace: 28 Mar 2006 16:42:23 -0700, 198.102.102.44
Lines: 20
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!198.102.102.44
Xref: solutions.advantagedatabase.com Advantage.Trigger:202
Article PK: 1136268

I may be changing triggers in 8.1 so their parent object is the table they
are defined on, instead of the database. This change will allow you to create
multiple triggers with the same name (provided they belong to different tables).

One drawback to this approach is it will potentially break existing applications.
If you have application code that reads trigger properties, or removes triggers,
those functions will start to fail unless the trigger name is qualified with
a table name. For example, if your application (or any of your utilities,
or sql scripts) currently execute a "drop trigger" statement, or call the
AdsDDRemoveTrigger API, or call the TAdsDictionary.RemoveTrigger method,
they will need to be changed to provide a table name with the trigger name.

I'm curious to get some community feedback. Do your applications even do
this? If they did, would the benefit outweigh the burden of modifying your
code?

J.D. Mullin
Advantage R&D


Francois Posted on 2006-03-29 00:54:51.0Z
Reply-To: "Francois" <fhaasbro@gmail.com>
From: "Francois" <francois@geedee.com.au>
Newsgroups: Advantage.Trigger
References: <886edc1510c9f8c8209e3085a5cc@devzone.advantagedatabase.com>
Subject: Re: trigger change that might affect your applications
Date: Wed, 29 Mar 2006 08:54:51 +0800
Lines: 40
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
NNTP-Posting-Host: 202.72.180.220
Message-ID: <4429da11@solutions.advantagedatabase.com>
X-Trace: 28 Mar 2006 17:51:29 -0700, 202.72.180.220
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!202.72.180.220
Xref: solutions.advantagedatabase.com Advantage.Trigger:203
Article PK: 1136269

Hi JD

I vote for the change.

I think that the cases where it will break code will be few and easily
detectable&fixable.

Regards
Francois

"Jeremy Mullin" <no@email.com> wrote in message
news:886edc1510c9f8c8209e3085a5cc@devzone.advantagedatabase.com...
> I may be changing triggers in 8.1 so their parent object is the table they
> are defined on, instead of the database. This change will allow you to
create
> multiple triggers with the same name (provided they belong to different
tables).
>
> One drawback to this approach is it will potentially break existing
applications.
> If you have application code that reads trigger properties, or removes
triggers,
> those functions will start to fail unless the trigger name is qualified
with
> a table name. For example, if your application (or any of your utilities,
> or sql scripts) currently execute a "drop trigger" statement, or call the
> AdsDDRemoveTrigger API, or call the TAdsDictionary.RemoveTrigger method,
> they will need to be changed to provide a table name with the trigger
name.
>
> I'm curious to get some community feedback. Do your applications even do
> this? If they did, would the benefit outweigh the burden of modifying your
> code?
>
> J.D. Mullin
> Advantage R&D
>
>


Thomas Steinmaurer Posted on 2006-03-29 17:07:13.0Z
Date: Wed, 29 Mar 2006 19:07:13 +0200
From: Thomas Steinmaurer <t.steinmaurer_dontbugmewithspam_@upscene.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: Advantage.Trigger
Subject: Re: trigger change that might affect your applications
References: <886edc1510c9f8c8209e3085a5cc@devzone.advantagedatabase.com>
In-Reply-To: <886edc1510c9f8c8209e3085a5cc@devzone.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 86.56.177.91
Message-ID: <442abdc0@solutions.advantagedatabase.com>
X-Trace: 29 Mar 2006 10:02:56 -0700, 86.56.177.91
Lines: 37
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.56.177.91
Xref: solutions.advantagedatabase.com Advantage.Trigger:204
Article PK: 1136270

Hello Jeremy,

> I may be changing triggers in 8.1 so their parent object is the table
> they are defined on, instead of the database. This change will allow you
> to create multiple triggers with the same name (provided they belong to
> different tables).
>
> One drawback to this approach is it will potentially break existing
> applications. If you have application code that reads trigger
> properties, or removes triggers, those functions will start to fail
> unless the trigger name is qualified with a table name. For example, if
> your application (or any of your utilities, or sql scripts) currently
> execute a "drop trigger" statement, or call the AdsDDRemoveTrigger API,
> or call the TAdsDictionary.RemoveTrigger method, they will need to be
> changed to provide a table name with the trigger name.
>
> I'm curious to get some community feedback. Do your applications even do
> this? If they did, would the benefit outweigh the burden of modifying
> your code?

It will break ADS LogManager, but as we are discussing a special version
of ADS LogManager for ADS 8.x taking advantage of the SQL scripting
facility in triggers, your proposed change wouldn't be a show-stopper
for us.

Any time-frame when 8.1 might hit the road? Thanks.


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com


Jeremy Mullin Posted on 2006-03-29 21:18:54.0Z
Date: Wed, 29 Mar 2006 21:18:54 +0000 (UTC)
Message-ID: <886edc1510d838c82152d8214784@devzone.advantagedatabase.com>
From: Jeremy Mullin <no@email.com>
Subject: Re: trigger change that might affect your applications
Newsgroups: Advantage.Trigger
References: <442abdc0@solutions.advantagedatabase.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-Newsreader: JetBrains Omea Reader 928.2
NNTP-Posting-Host: 198.102.102.44
X-Trace: 29 Mar 2006 14:15:33 -0700, 198.102.102.44
Lines: 40
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!198.102.102.44
Xref: solutions.advantagedatabase.com Advantage.Trigger:205
Article PK: 1136271

Thanks Thomas,

I actually had your name specifically mentioned in my design, and planned
on sending you an e-mail describing my changes and their effects.

Right now we're looking at late summer/early fall for the 8.1 release.

J.D. Mullin
Advantage R&D

> Hello Jeremy,
>
>> I may be changing triggers in 8.1 so their parent object is the table
>> they are defined on, instead of the database. This change will allow
>> you to create multiple triggers with the same name (provided they
>> belong to different tables).
>>
>> One drawback to this approach is it will potentially break existing
>> applications. If you have application code that reads trigger
>> properties, or removes triggers, those functions will start to fail
>> unless the trigger name is qualified with a table name. For example,
>> if your application (or any of your utilities, or sql scripts)
>> currently execute a "drop trigger" statement, or call the
>> AdsDDRemoveTrigger API, or call the TAdsDictionary.RemoveTrigger
>> method, they will need to be changed to provide a table name with the
>> trigger name.
>>
>> I'm curious to get some community feedback. Do your applications even
>> do this? If they did, would the benefit outweigh the burden of
>> modifying your code?
>>
> It will break ADS LogManager, but as we are discussing a special
> version of ADS LogManager for ADS 8.x taking advantage of the SQL
> scripting facility in triggers, your proposed change wouldn't be a
> show-stopper for us.
>
> Any time-frame when 8.1 might hit the road? Thanks.
>


Thomas Steinmaurer Posted on 2006-04-01 08:04:43.0Z
Date: Sat, 01 Apr 2006 10:04:43 +0200
From: Thomas Steinmaurer <t.steinmaurer_dontbugmewithspam_@upscene.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: Advantage.Trigger
Subject: Re: trigger change that might affect your applications
References: <442abdc0@solutions.advantagedatabase.com> <886edc1510d838c82152d8214784@devzone.advantagedatabase.com>
In-Reply-To: <886edc1510d838c82152d8214784@devzone.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 86.56.177.91
Message-ID: <442e3311@solutions.advantagedatabase.com>
X-Trace: 1 Apr 2006 01:00:17 -0700, 86.56.177.91
Lines: 16
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.56.177.91
Xref: solutions.advantagedatabase.com Advantage.Trigger:206
Article PK: 1136273

Hello Jeremy,

> I actually had your name specifically mentioned in my design, and
> planned on sending you an e-mail describing my changes and their effects.

Thanks.

> Right now we're looking at late summer/early fall for the 8.1 release.

Ok, thanks. Enough time for us to jump onto the 8.x train with a special
version of ADS LogManager.


Thanks again,
Thomas