Graham Keys wrote > > No problems. All I'm really looking for is how to set this > global setting. > I must be able to set it to never timeout or to timeout after so many > seconds, even if it does affect every user. > > Thanks, > Graham >
It is an installation parameter, has to be set using DBM* and will be used starting from the next server-start. Its maximum value in seconds is 100 000 --> more than 27 hours. It is not NEVER, but for real applications more than one day is 'never', I assume. Elke SAP Labs Berlin > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Dittmar > Sent: Monday, October 20, 2003 3:54 PM > To: [EMAIL PROTECTED] > Subject: Re: REQUEST_TIMEOUT > > Graham Keys wrote: > > Are we talking about the same timeout setting? My > understanding of the > > timeout setting on connect is that it is the maximum inactivity time > between > > SQL statements. What I'm looking for is the lock timeout > setting - ie. > > denotes the maximum amount of time (in seconds) you should > have to wait > for > > a lock to be released. > > Sorry for the misunderstanding. The lock request timeout is indeed > global and cannot be changed for individual sessions. > > Daniel Dittmar > > -- > Daniel Dittmar > SAP DB, SAP Labs Berlin > [EMAIL PROTECTED] > http://www.sapdb.org > > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
