>>>>> P.S. This discussion is purely theoretical as compatibility has already >>>>> been restored in the meantime. >>>> >>>> I never said a properly written application could be affected, I said >>>> something >>>> has clearly changed as existing applications suddenly return the wrong >>>> result. >>> >>> A change that only affects poorly written applications, which could not >>> work correctly in the first place, is not an appropriate "straw man" for >>> any argument. >> >> Exactly why do current applications work then? What is different now? >> >> I've just checked the IBX components source, for example, and it >> explicitly >> checks >> for null before asking for data. >> >> Doesn't isql do the same? Thomas' first e-mail showed the isql prompt with >> SHOW DOMAIN command >> >> The isql session created only the domains. There was no SHOW DOMAIN >> command there. > > There was in your e-mail to the dbw-beta test list. > > (reading it again) > > Oh wait, that showed something different, my bad. > > I wonder then, Thomas, can you reproduce this issue with the IBX components?
Ehm, why do we care about IBX? ;-) T. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
