Hi have a look at http://www.mmbase.org/docs/reference/taglib/listnodes.jsp See constraints attribute of list, but notice that it is not necessary to prefix the field names with `node manager' names. You can put the field names in [] to enable 'key word escaping'. E.g. in some databases 'status' is not a valid field name. [status] will translate the field name in the right way. Consider using 'constraint' tags and listnodescontainer for more flexibility. see: constraints attribute of list | constraint
-----Original Message----- From: [EMAIL PROTECTED] on behalf of Simon Groenewolt Sent: Fri 2004-05-07 6:17 PM To: mmbase devlist Cc: Subject: constraints on fields that are not premitted in the database 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
<<winmail.dat>>
