Uli

>As Roy told you: if there is an index on the field you are grouping the
>result can be sensitive.

As they say in all the best pantos "OH no I didn't"

Roy Lambert

Mind you it was open to mis-interpretation.

Michael,

> Are you sure ? I just tried and the result was read-only.
> (I have an index on the group field)

I am very sorry: I misread your posting and referred to "order by"
instead of "group by".

You are right - the result is never sensitive:

The manual says:

Queries that retrieve data from a single table will generate a sensitive
result set provided that:
1) The user or developer requests a sensitive result set cursor. Please
see the DECLARE statement for more
information on requesting a a sensitive or insensitive result set
cursors in SQL/PSM routines, and your productspecific
manual for requesting sensitive or insensitive cursors in client
applications.
2) There is no DISTINCT keyword in the SELECT statement.
3) All SELECT expressions are either a column reference or a computed
column that does not contain any
aggregate functions (MIN, MAX, SUM, etc.), sub-queries, or non-native
function references (functions created via
the CREATE FUNCTION statement). Computed columns are read-only in the
sensitive result set cursor and
cannot be modified.
4) There is no GROUP BY clause in the SELECT statement.
5) There is no ORDER BY clause in the SELECT statement, or there is an
ORDER BY clause that minimally
matches the columns, and the collations defined for the columns, in an
existing index in the source table.
6) There are no correlated sub-queries in the JOIN or WHERE clauses of
the SELECT statement.
7) There is no RANGE clause in the SELECT statement.

Uli