View Single Post
  #6  
Old October 19th, 2011, 06:46 PM
Mobhack's Avatar

Mobhack Mobhack is offline
National Security Advisor
 
Join Date: Mar 2005
Location: Dundee
Posts: 5,994
Thanks: 488
Thanked 1,928 Times in 1,254 Posts
Mobhack is on a distinguished road
Default Re: Belgium OOB error report

One problem with using "national" names for exactly the same things is that it is an extreme PITA when it comes to OOB maintenance. So often it'll be whatever the majority or "home producer" unit name it is for the thing that we use. Especially for smaller/minor OOBs.

Consider for example this bit of SQL which is attempting to dump all the varicose "centurions" in the extracted OOB database:

Select U.NationID,N.NationName,U.name,U.slot,u.SteelHullf ront,u.steelhullside,u.steelhullrear,u.steelturret front,u.steelturretside,u.steelturretrear,u.steelt op
from Units U, NationNames N
where ( ( LOWER(U.name) like "%centurion%")
OR (LOWER(U.name) like "%semel%")
OR (LOWER(U.name) like "%olifant%")
OR (LOWER(U.name) like "%sh'ot%")
OR (LOWER(U.name) like "%pz%%55%")
OR (LOWER(U.name) like "%pz%%57%")
OR (LOWER(U.name) like "%strv%%81%")
OR (LOWER(U.name) like "%strv%%101%")
OR (LOWER(U.name) like "%strv%%102%")
OR (LOWER(U.name) like "%strv%%104%")
OR (LOWER(U.name) like "%tariq%"))
AND U.nationID=n.nationID
order by u.steelhullfront


- and there is quite probably some odd variation in the name for the darned thing that I have missed out ...

Andy
Reply With Quote