> SS> Yes, but now you have to told to FB explicitly which part of number have > SS> to be discarded. > > And you still could do this, as you wish :) You remain with full > control, if/when you prefer to have it. I guess the proposed > enhancement will be useful for 99% of the cases, when user don't care > about loosing some accuracy in the middle of the calculation, but > still cares about accuracy of stored data (what you store is exactly > what you get when you retrieve it). For the other 1%, user still has > full control doing his own casts as desired. OK, can you make example how engine (with you extension) will handle this:
select 1.000000000 / 1.0000000000 from rdb$database and in same time this select 0.000000001 / 9.0000000000 from rdb$database and same time this select 1.000000001 / 0.0000000001 from rdb$database > > SS> Can you give me real example with decimal casting? > > What do you mean? I don't understand your situation from practical point of view. If you can accept losses during computing, why can't you accept DOUBLE PRECISION? I will be happy, if firebird will support int128, NUMERIC up to scale 31++ and many more :). Slavek ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
