> > Over all 12 years of FB development it became clear that *remaining* > > dialect 1 users simply can't switch at all (old legacy app, they > > certainly switch with new app. versions), so giving them another 2 > > years inserting deprecation version before removal will not help them > > in any significant way.
> I hope to be wrong and that changed, but AFAIR, the legacy dialects are > never removed mainly because BroadView systems are not prepared for it, > and they are FF sponsors. This is completely incorrect. BroadView has **never** attempted to prevent any change to the Firebird code base. In fact, we have only aver pushed for new features to be added. We have, however, suggested/advocated* that there are significant issues with Dialect 3 which make migration of legacy application very difficult (yes, the BroadView application continues to use Dialect 1). The most significant issue is that way that the precision that math operations have in Dialect 3 vs. Dialect 1 and the need to add CAST operands to existing syntax (where none is required in Dialect 1). Sean P.S. we have advocated/argued just like any other participants in this list. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
