Re[2]: [Firebird-devel] Max transaction duration

[Daniel R. <da...@ac...>]

Hi all,

>> I guess that would depend on the units used.  If you
>> can set the
>> number of months that a transaction can be open,
>> that seems OK.
>> If the units are hours or minutes, the chance of
>> killing a major
>> report or year-end process is high enough to scare
>> me off.
[...snip...]
> I'm thinking in minutes or hours, but if you don't want to use this feature
> you can set it to 0 so the transaction will never be closed by the server.
> I think that a feature like this will be a very usefull for critical systems
> with hight number of users and for tunning new applications.

I, too, like the idea of a maximum transaction duration.

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.
- Default duration defined at the database level to be able to
override the server's default duration.
- Pass the duration upon connection to override the default duration,
so that in some circumstances the duration can be extended to perform
i.e. the year-end processing/reports.

I know that this might require some changes to the API.

Just my 2 cents.

-- 
Best regards,
 Daniel Rail
 Senior System Engineer
 ACCRA Group Inc. (www.accra.ca)
 ACCRA Med Software Inc. (www.accramed.ca)