constraints on fields that are not premitted in the database

[Simon Groenewolt]

hi,

I noticed that using a field 'no' on hsqldb was translated to 'm_no' in 
the database.

However, if I want to specify a constraint on a listnodes I cannot use 
'no' but have to use 'm_no' to get it to work. This is using 1.7 but I 
remember this was also the case in 1.6.5.

This could be fixed by also translating the constraint fields couldn't it?

I found bug #5228 that reports this and contains a maintainer notice 
with a workaround, but shouldn't this be fixed? The problem is 
particularly nasty if you develop and deploy on different databases so 
you won't notice it at first.

  Simon