On 01-01-2012 15:11, Jesús García wrote: > > I think the question is if it is neccesary and good for Firebird, and if the > pros of having transactions id of 64bits are better that the cons of not > having it. From my POV using 32 bits id is an important restriction in the > engine, and i would prefer not having it. >
This is the wrong way to deal with the problem IMO. Let something like sweep consolidate old transactions in only one, concurrently with user operations. In that way, there will be in the database header the number of the first transaction. The last possible transaction is (first - 1). When needed, 'first' is increased, so as last. Nobody needs more than 4 billions active transactions concurrently. Adriano ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
