I think allowing wait_timeout to be set per session is enough. Interactive_timeout always seemed like a feature with not enough benefit to justify it's existence. Per user wait timeouts would be more interesting than a timeout for clients that set CLIENT_INTERACTIVE and ones that don't.
On Wed, Mar 18, 2009 at 10:21 AM, Brian Aker <[email protected]> wrote: > Hi! > > The option "sysdate-is-now"... what should this be? It is basically there > for Oracle compatibility, but it does give you the advantage of a time > creation that occurs in row. > > The option "interactive_timeout". I've found over the years that users will > be confused about this and the wait timeout. What should the functionality > be? Should we let clients override the system maximums? > > Cheers, > -Brian > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > -- Eric Bergen [email protected] http://www.provenscaling.com _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
