Skip to Content.
Sympa Menu

freetds - Re: [freetds] FIRE_TRIGGERS hint

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: michael.peppler AT bnpparibas.com
  • To: freetds AT lists.ibiblio.org
  • Subject: Re: [freetds] FIRE_TRIGGERS hint
  • Date: Wed, 20 Sep 2006 07:40:21 +0200

I'm pretty sure that the Sybase utilities set such options via the
ct_options() call, and so don't use any SQL at all to do this.

Michael




Internet
jklowden AT freetds.org@lists.ibiblio.org - 19.09.2006 04:36

Please respond to freetds AT lists.ibiblio.org
Sent by: freetds-bounces AT lists.ibiblio.org
To: freetds
cc:
Subject: Re: [freetds] FIRE_TRIGGERS hint


Constantin Vasilyev wrote:
> Could it be added, then. I'm not sure if this worth submitting the
> patch.
>
> And another idea. Sometime (like in case of pulling data out of indexed
> views) database connection which freebcp opens requires some options
> (like ANSI_NULLS) to be set before fetching the data. Some of those
> options work if submitted within the same batch with SELECT statement,
> so queryout mode may be used for them, but some work only if placed in
> separate batch. For such cases it might be useful to add an option to
> which allows to run some commands on the server (or simply set
> particular options for the connection) before pumping the data.

Good ideas, both. I wonder how Microsoft and Sybase deal with that in
their utilities? Do you have an example of a session setting that must
be in a separate batch? Because other than that, "queryout" should do the
trick.

--jkl
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds


This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.

---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.





Archive powered by MHonArc 2.6.24.

Top of Page