My unittests indicated that this issue was introduced by modifications outside of the dbsq (query) classes. My guess is it's in the storage classes. The dbsq classes do rely on storage code when generating SQL statements.
There is no reference anywhere to storage classes or even use of the JDBC2NodeInterface. The only possible is the 'disallowed2allowedfield' map, which is passed by the storagelayer, but that can only be a cause if 'numbercount' is included as a reserved word.
I am a bit stumped, can't find any code that mangles the aliasses.
Maybe this is a 1.7.0 bug? Can you verify it still present in 1.7.1 (recent CVS version)?
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
