From: Ann W. H. <aha...@ib...> - 2002-12-12 15:57:40
|
At 07:01 PM 12/11/2002 -0300, Juarez Rudsatz wrote: >- Default duration defined at user level to be able to override the server's >default configuration. If the problem is users who discover an interactive query tool and leave transactions open for days, then requiring that the user transaction limit itself is probably not going to work. >Here's one way of designing it: >- Default duration defined at the server level, so when creating a new >database it will use that default duration. That bothers me somewhat, probably because I'm not entirely happy with the server model starting with server logins. Yes, sometimes a single machine will host a number of related databases. More often, just a single database. And sometimes, a number of unrelated databases. That case really can't be supported now. >- Default duration defined at the database level >- Pass the duration upon connection > >I know that this might require some changes to the API. Actually that can all be done with connection and transaction parameters - yes, we'd need to add parameters, but that doesn't fundamentally change the API Regards, Ann www.ibphoenix.com We have answers. |