> -----Original Message----- > From: Ann Harrison [mailto:aharri...@nuodb.com] > Sent: Martes, 06 de Marzo de 2012 19:10 > > Having started this discussion by agreeing with Claudio, now > let me suggest that I was probably wrong. I'll think about it > a bit more, but finding a way of extending blr compatibly > seems like a much better idea. That lets old databases > continue to work and avoids the whole discussion of what > other features to drop. More tomorrow.
Ann, I hope you will come with an interesting solution. However, let's recap: - If the BLR version number doesn't serve to upgrade BLR, then it's completely useless. - The original proposal was to upgrade BLR, nothing more. Other person wanted to drop BLR v4 and then dialect 1 and the discussion became fuzzy and out of bounds. The original proposal NEVER intended to remove the old BLR and the old dialect. - The only problem that a new BLR version doesn't solve is when you want to go back to a previous server version, but if you try to use some FB3's new DSQL feature in FB2.0, it's going to fail, right? So, what's different? Some new BLR verbs don't exist in the original FB1.0, despite the BLR version not being increased. When BLR v5 was invented, older servers speaking BLR v4 couldn't understand it... but the world didn't explode. C. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
