> > Disk speed was always the issue, it doesn't increase that fast as > CPU/memory speed. So the on-disk size always matters quite a lot. > > > Dmitry
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. The flag option is good because only the databases that need high transactions numbers pay for their use, but as you wrote, the engine code become more complicated. My customer with highest transactions number would work, by the moment, for 7/8 years without stop, but i would sleep better if i have not to worry about that, and if i have not have to explain that restriction to my customer, what can make think that firebird is not so good as i tell him. Firebird 3 is growing, and now may be the moment to change it. FB 3 will live for years and Systems require more and more. I used Firebird 1 years ago, but now our clients with more work load wouldn't work with that version. Is there any measurement of the real impact of the change? Jesus ------------------------------------------------------------------------------ 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
