Dynamic query woes.

[Daniel Pitts <Da...@cnet.com>]

I have a very generic query which has different column names, depending
on what was passed to it.
<select id="query" resultClass="java.util.HashMap" parameterClass="map">
        SELECT $columns$ FROM $from$ WHERE $where$
</select>

It works fine the first time. And it even works fine if $columns$
doesn't change.  However, if $columns$ had (for instance) "my_column" in
one query, but then it had "another_column" in a later query, the last
query fail with "no such column 'my_column'"

Is this a bug, or a feature? Also, is there a work-around?
Thanks.

Re: Dynamic query woes.

[Ted Schrader <ts...@gmail.com>]

Here are some juicy details on the remapResults attribute:

http://opensource2.atlassian.com/confluence/oss/pages/viewpage.action?pageId=3057

Ted

Re: Dynamic query woes.

[Larry Meadors <lm...@apache.org>]

Add remapResults="true" in the select tag.

There is a performance hit, but it will work.

Larry


On 3/23/06, Daniel Pitts <Da...@cnet.com> wrote:
> I have a very generic query which has different column names, depending
> on what was passed to it.
> <select id="query" resultClass="java.util.HashMap" parameterClass="map">
>         SELECT $columns$ FROM $from$ WHERE $where$
> </select>
>
> It works fine the first time. And it even works fine if $columns$
> doesn't change.  However, if $columns$ had (for instance) "my_column" in
> one query, but then it had "another_column" in a later query, the last
> query fail with "no such column 'my_column'"
>
> Is this a bug, or a feature? Also, is there a work-around?
> Thanks.
>