FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> Dan Mohn wrote:
> > ZIGLIO, Frediano, VF-IT wrote:
> > > I didn't committed this patch cause
> > > - I added a "default_query_timeout" on HDBC. Is this required??
> > > - is the way query_timeout is reset to default correct??
> > > - should we handle case when statement is created before 
> connection??
> > 
> > James K. Lowden wrote:
> > >> For me to answer these questions, I will have to study the
> > documentation. I won't be able to do that until next week.  Perhaps
> > someone else knows, or would like to research it? <<
> > 
> > I'm not sure exactly what is being asked , but given a bit more
> > direction, I can try and research "it".
> 
> According to the ODBC standard, 
> 
> 1.  Does an ODCBC connection handle need a timeout?  
> 2.  Is it OK to set a statement timeout before the connection is
> established?  
> 3.  Under what conditions does the timeout revert to its default?  
> 

Well.. I committed the patch adding a small note. Mainly 
- default_query_timeout is needed cause there is no other space to keep
this data
- query_timeout was reset even before the patch. However should
tds->query_timeout be set using login/connect dbc timeouts??
- we handle the case where timeout is set before connection... and even
after!

1. well... there connect and login timeout. Connect is like libTDS
connect_timeout while login should be used for queries during
SQLConnect/SQLDriverConnect. If we change database
(SQLSetConnectAttr(SQL_ATTR_CURRENT_CATALOG)) what timeout should be
used??
2. I don't know but currectly it works
3. good point. Mainly queries you can post have a statement (and so you
should use statement timeout) but in conditions described in 1 I don't
know...

freddy77