Bug 995 - controlling query results in the default query results dialog
: controlling query results in the default query results dialog
Status: NEW
: Chameleon
Widget
: 2.2
: PC All
: P2 enhancement
: FUTURE
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-03-30 11:13 by
Modified: 2006-09-05 16:29 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-03-30 11:13:54
We really need to add a way of controlling query results in the default query
results dialog, metadata seems reasonable (perhaps a new attribute on the query
widget to indicate the name of a metadata field that contains the field names
would be the right thing to do?) 

MapServer uses "result_fields" metadata.  It would be ideal to maintain some
consistency with MapServer's method so map files can be re-used without changes.
------- Comment #1 From 2005-05-27 09:46:15 -------
I agree it would be a nice enhancement. Probably in 2.3. Setting to FUTURE.For
now there's the query customisation page to help.

http://chameleon.maptools.org/tiki/tiki-index.php?page=QueryWidgetCustomizingResults

You can also check the new LinkQuery widget. It's a regular query widget, except
that it opens a custom page (home made) to display your result.
------- Comment #2 From 2006-09-05 13:15:50 -------
Any movement or potential plans for addressing this?  My customising code isn't
working too well, but before I review it, I just wanted to check this.
------- Comment #3 From 2006-09-05 16:29:22 -------
You can already specify a HEADER in the layer. 
HEADER "NAME^Name|UNIQUE_KEY^Key"

Or directly in the widget:
<CWC2 Type="Query"...>
    <TABLEHEADER LAYER="popplace" HEADER="NAME^Name|UNIQUE_KEY^Key"/>
</CWC2>

Does that meet the requirement of this bug?
Can we mark it as fixed?