On 19 Dec 2009, at 16:19, John Denker wrote: > Maybe the code should be made more robust so that this > is not a fault condition. > > This is not the first time in history that code has > needed to perform a join on two databases that are > not in one-to-one correspondence.
Well I wrote the code in question, and preferred to reject a corrupt data set rather than blindly carrying on - I am also a bit reluctant to encourage casual users to mess with a somewhat archaic data format. Nevertheless, it's pretty easy to tolerate this case, a fix will appear soon - the problem is some things aren't going to work, notably ILS <-> runway references. James ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel