FreeTDS Development Group

["David Chang" <dchang AT fsautomation.com>]

G,

I'm not familiar with dbconnect().  It's not part of Open Client CT-Lib. 
Maybe it's a function your folks wrote that abstracts the login process. 
For more information on CT-Lib, look at this document: 
http://infocenter.sybase.com/help/topic/com.sybase.dc32840_1500/pdf/ctref.pdf

DC

----- Original Message ----- 
From: "Garudappa, Gangegowda (iGATE)" <gangegowda.garudappa AT rbc.com>
To: <freetds AT lists.ibiblio.org>
Sent: Wednesday, March 12, 2008 10:44 AM
Subject: [freetds] FW: FreeTDS Digest, Vol 62, Issue 7


> How to connect to Sybase ASE using C program with sybase open client
> libraries on Windows platform.
>
> Do I need to mention any configurations explicitly or passing  a
> parameter to dbconnect() works as it is?
> Any inputs are much appreciated.
>
> Regards.
> Gangegowda K.G
> ------------------------------
>
> Message: 2
> Date: Sat, 8 Mar 2008 12:20:28 -0800
> From: "David Chang" <dchang AT fsautomation.com>
> Subject: Re: [freetds] Migrating code from HPUX to Windows.
> To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
> Message-ID: <000301c8821b$c2919db0$9733a8c0@rudolf>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> Answers are below...
>
> ----- Original Message -----
> From: "Garudappa, Gangegowda (iGATE)" <gangegowda.garudappa AT rbc.com>
> To: <freetds AT lists.ibiblio.org>
> Sent: Saturday, March 08, 2008 10:24 AM
> Subject: [freetds] Migrating code from HPUX to Windows.
>
>
> > We are migrating one of the legacy Unix application to Windows VS .Net
> > environment.
> > We are planning to use freeTDS8.2/6.4 and we have downloaded it. But
> we
> > did not see any options for compiling/building freeTDS application on
> > Win 2003 Server using VS .NET.
> >
> > We would like to know the following,
> >
> > 1) Are there already a database stubs/libraries/functions available in
> > Microsoft/Visual Studio(VC++) for connecting and performing database
> > operations on Sybase database running on Solaris box.
>
> Yes.  If you are using Sybase ASE, you can download the PC client
> software
> for ASE from Sybase at
> http://downloads.sybase.com/swd/detail.do?relid=6942&ebf=12305&baseprod=
> 2&client=search ,
> however, you need a valid Sybase login (I think this means you have to
> have
> a valid maintenance contract with Sybase).
>
> Once you have these libraries and include files, you can write (or port)
>
> DB-Library and CT-Lib applications in Microsoft C++.
>
> Otherwise, you can use FreeTDS.  I've only used the DB-Library API for
> FreeTDS.  I'm not sure if they have a CT-Lib API.
>
> Lastly, you can always use Cygwin (UNIX API layer) and compile FreeTDS
> with
> gcc and the port might be easier.
>
> > 2) Is it possible to use existing HPUX open-client libraries on
> Windows
> > side to perform Sybase database operations running on Solaris box. The
> > Unix application is compiled using 'cc' with all the sybase libraries.
> > Is it possible to use the Unix database related libraries to customize
> > our application.
>
> Sure.  Once you have the Net-Lib and DB-Lib layers, you can communicate
> with
> any ASE server regardless of O.S.
>
> > 3)What are the essential things are required from freeTDS for
> connecting
> > to a database server running on Solaris machine.
>
> Once the application compiles, you just need to set-up the proper
> freetds.conf file.  There are lots of examples and it's fairly simple.
> If you're already familiar with the 'interfaces' file in Sybase, you
> should
> have no problems with the freetds.conf file.
>
> > 4) How to compile/build freeTDS in MS-VS .Net 2005 environment.
>
> What specific question do you have about this?  Generally you do a
> 'configure' and a 'make'.
>
> > 5) How to integrate/customize our application with freeTDS.
> >
> > We are running on below platform,
> > 1. The database will be running on : Sybase ASE 12.5
> > Sparc/Solaris2.8
> > 2. The application runs and connects to database from : Windows
> > 2003 Server Visual Studio with .Net 2005 environment using VC++
> > Please correct us if we are missing anything here because this is the
> > first time we are trying to do this.
> > Please let us know if there is any alternative mechanism or different
> > open source code/libraries available to implement the same.
> > We are running on below platform,
> > 1. The database will be running on : Sybase ASE 12.5
> > Sparc/Solaris2.8
> > 2. The application runs and connects to database from : Windows
> > 2003 Server Visual Studio with .Net 2005 environment using VC++
>
> Is it a DB-Lib application?  If so, you only need to make modifications
> to
> the Windows specific things (like filenames that use backslashes, and
> multiple hard drive letters) or use the Cygwin API layer.  The DB-Lib
> stuff
> pretty much works.
>
> DC
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 10 Mar 2008 10:37:29 +0100
> From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
> Subject: Re: [freetds] ODBC auto-commit mode nonfunctional with
> Microsoft?
> To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
> Message-ID:
> <72EBB5FADDA71343B78E1F09FF471F6E452736 AT OBOMEXO02.omnitel.it>
> Content-Type: text/plain; charset=us-ascii
>
> > Frediano Ziglio wrote:
> > > > I was experimenting with the DB session's
> > > > "auto-commit mode". I found that it doesn't work for MS
> > SQL, and it
> > > > does  work for Sybase.
> > >
> > > Too few for a bug report... auto-commit mode is the default
> > mode (not
> > > default is no auto-commit). 95% of unittests work in
> > auto-commit mode so
> > > why do they work?? Perhaps the problem is in no auto-commit...
> >
> > I believe he means that passing SQL_ATTR_AUTOCOMMIT with
> > SQL_AUTOCOMMIT_OFF/SQL_AUTOCOMMIT_ON to SQLSetConnectionAttr doesn't
> > change whether or not the connection is in autocommit mode.
>
> I downloaded OTL and looked at the source. The problem is that FreeTDS
> does not set properly auto-commit to off before connection but only
> after.
> I think it will require some extra rows... just set implicit transaction
> after connection if auto-commit is off... change similar to
> change_database call...
>
> freddy77
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 10 Mar 2008 11:48:52 +0100
> From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
> Subject: Re: [freetds] ODBC auto-commit mode nonfunctional with
> Microsoft?
> To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
> Message-ID:
> <72EBB5FADDA71343B78E1F09FF471F6E452737 AT OBOMEXO02.omnitel.it>
> Content-Type: text/plain; charset=us-ascii
>
> > Frediano Ziglio wrote:
> > > > I was experimenting with the DB session's
> > > > "auto-commit mode". I found that it doesn't work for MS
> > SQL, and it
> > > > does  work for Sybase.
> > >
> > > Too few for a bug report... auto-commit mode is the default
> > mode (not
> > > default is no auto-commit). 95% of unittests work in
> > auto-commit mode so
> > > why do they work?? Perhaps the problem is in no auto-commit...
> >
> > I believe he means that passing SQL_ATTR_AUTOCOMMIT with
> > SQL_AUTOCOMMIT_OFF/SQL_AUTOCOMMIT_ON to SQLSetConnectionAttr doesn't
> > change whether or not the connection is in autocommit mode.
>
> Fixed. See http://freetds.sourceforge.net/post82.diff.gz
>
> freddy77
>
>
> ------------------------------
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
>
>
> End of FreeTDS Digest, Vol 62, Issue 7
> **************************************
> _______________________________________________________________________
>
> This email is intended only for the use of the individual(s) to whom it is 
> addressed and may be privileged and confidential.
> Unauthorised use or disclosure is prohibited. If you receive This e-mail 
> in error, please advise immediately and delete the original message.
> This message may have been altered without your or our knowledge and the 
> sender does not accept any liability for any errors or omissions in the 
> message.
>
> Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux 
> droits et obligations qui s'y rapportent.
> Toute diffusion, utilisation ou copie de ce message ou des renseignements 
> qu'il contient par une personne autre que le (les) destinataire(s) 
> désigné(s) est interdite.
> Si vous recevez ce courriel par erreur, veuillez m'en aviser 
> immédiatement, par retour de courriel ou par un autre moyen.
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds