It's hard to keep track of every change. I wondering if anyone else has noticed this. In 4.8 with PostGIS one could do queries like:
...&mode=itemquery&qitem=station&qstring=12345678&... and the PostGIS driver would build the appropriate SQL. However, with 4.10 this doesn't seem to be the case. I get an error that basically says that '12345678' is not a valid PostGIS column. I can work around with a URL like: ...&mode=itemquery&qstring=(station=12345678)&... I kinda liked the flexibility of the 4.8 mechanism... Might have had to do with quoting of the search string but I'm not positive about that. Steve
