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.

set option -gf

3 posts in General Discussion Last posting was on 2007-10-10 03:20:43.0Z
Chris Posted on 2007-10-09 09:21:33.0Z
From: "Chris" <Chris@gmail.com>
Newsgroups: ianywhere.public.general
Subject: set option -gf
Lines: 18
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: 125.160.232.11
X-Original-NNTP-Posting-Host: 125.160.232.11
Message-ID: <470b481d@forums-1-dub>
Date: 9 Oct 2007 02:21:33 -0700
X-Trace: forums-1-dub 1191921693 125.160.232.11 (9 Oct 2007 02:21:33 -0700)
X-Original-Trace: 9 Oct 2007 02:21:33 -0700, 125.160.232.11
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6361
Article PK: 2852

on isql i run *set option -gf*

and then the result has something like

"stop"
"system"
"temporary"
...
<PARAMETER_VALUE>

what does it mean? has it prevented trigger from firing for temporary or
permanently?

how to reverse the effect? turning trigger firing back to ON again?

thanks


"Nick Elson" < Posted on 2007-10-09 13:51:15.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <470b481d@forums-1-dub>
Subject: Re: set option -gf
Lines: 52
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: nicelson-d620.sybase.com
X-Original-NNTP-Posting-Host: nicelson-d620.sybase.com
Message-ID: <470b8753$1@forums-1-dub>
Date: 9 Oct 2007 06:51:15 -0700
X-Trace: forums-1-dub 1191937875 10.25.98.247 (9 Oct 2007 06:51:15 -0700)
X-Original-Trace: 9 Oct 2007 06:51:15 -0700, nicelson-d620.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6369
Article PK: 4724

I do need to ask, why do you want to disable
the firing of all your triggers?

As to using that from dbisql, that is not a settable
option but a server switch. You can add that as in

dbsrv[N] -gf

but be careful of doing that since it can break
a number of things when used indescriminently.

The settable option you may be looking for

set option "FIRE_TRIGGERS"='off';

which could be set through dbisql but, again,
with the same caveats as above.

As to "stop" "system" "temporary" ...
you have me a little befuddled as to what
your are actually seeing.

To return the server back to normal, set the
option back on or remove the -gf switch.

This is a database wide setting (all connections
are affected) so be very careful of the need to
do this. Adding special code to the few triggers
you need to be affected is usually a more sane
way of going.

"Chris" <Chris@gmail.com> wrote in message news:470b481d@forums-1-dub...
> on isql i run *set option -gf*
>
> and then the result has something like
>
> "stop"
> "system"
> "temporary"
> ...
> <PARAMETER_VALUE>
>
> what does it mean? has it prevented trigger from firing for temporary or
> permanently?
>
> how to reverse the effect? turning trigger firing back to ON again?
>
> thanks
>
>


Chris Posted on 2007-10-10 03:20:43.0Z
From: "Chris" <Chris@gmail.com>
Newsgroups: ianywhere.public.general
References: <470b481d@forums-1-dub> <470b8753$1@forums-1-dub>
Subject: Re: set option -gf
Lines: 64
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; Response
NNTP-Posting-Host: 125.160.239.190
X-Original-NNTP-Posting-Host: 125.160.239.190
Message-ID: <470c450b@forums-1-dub>
Date: 9 Oct 2007 20:20:43 -0700
X-Trace: forums-1-dub 1191986443 125.160.239.190 (9 Oct 2007 20:20:43 -0700)
X-Original-Trace: 9 Oct 2007 20:20:43 -0700, 125.160.239.190
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6374
Article PK: 4727

there are some points in my application that need to bypass triggers, yet
since the effect of the FIRE_TRIGGERS option also disable RI (which I do not
want) then I should find another way.

thanks Nick

"Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@> wrote in message
news:470b8753$1@forums-1-dub...
>I do need to ask, why do you want to disable
> the firing of all your triggers?
>
> As to using that from dbisql, that is not a settable
> option but a server switch. You can add that as in
>
> dbsrv[N] -gf
>
> but be careful of doing that since it can break
> a number of things when used indescriminently.
>
> The settable option you may be looking for
>
> set option "FIRE_TRIGGERS"='off';
>
> which could be set through dbisql but, again,
> with the same caveats as above.
>
> As to "stop" "system" "temporary" ...
> you have me a little befuddled as to what
> your are actually seeing.
>
> To return the server back to normal, set the
> option back on or remove the -gf switch.
>
> This is a database wide setting (all connections
> are affected) so be very careful of the need to
> do this. Adding special code to the few triggers
> you need to be affected is usually a more sane
> way of going.
>
> "Chris" <Chris@gmail.com> wrote in message news:470b481d@forums-1-dub...
>> on isql i run *set option -gf*
>>
>> and then the result has something like
>>
>> "stop"
>> "system"
>> "temporary"
>> ...
>> <PARAMETER_VALUE>
>>
>> what does it mean? has it prevented trigger from firing for temporary or
>> permanently?
>>
>> how to reverse the effect? turning trigger firing back to ON again?
>>
>> thanks
>>
>>
>
>
>