Group By issues with BLOBs

rbuser

Using RBuilder v7.03/D7/DBISAM 3

Adding one field to groups seems to add all the fields (behind the
scenes). Returning to the Groups tab frequently reveals all of
the fields as being assigned. The generated SQL includes all the fields
in the GROUP BY . I cannot remove fields that have been assigned
in the GROUPS tab (except by removing the field in the FIELDS tab).

If one of those fields is a BLOB an SQL error is generated (as
expected).

I can solve the problem by direct editing of the SQL (but that is
something I would prefer to avoid) or not selecting the field in the
FIELDS tab.

Is there a known issue with GROUP BY or is it something unique to my
data or I am using the designer incorrectly?

Jon


--
Jon Lloyd Duerdoth
Welsh Dragon Computing
http://www.welshdragoncomputing.ca
Visit All Saints' Kingsway Anglican Church
http://www.allsaintskingsway.ca

nicocizik

Hi Jon,

Correct me if I'm wrong, but I was under the impression that when creating
grouped queries, all non aggregate fields are required to be in the GROUP BY
and you are also unable to group by a blob field. This would prevent anyone
from grouping a query that selects a blob field. I believe this is the
assumption the query designer makes and is the reason you are unable to get
your query to work. You may be able to exclude the blob field in the
grouped query and link in another query with only that field selected when
you need it.

Out of curiosity, you mentioned you could solve this by editing the SQL by
hand. Is there a special way in DBISAM to work around this limitation of
query grouping?

--

rbuser

Nico,
I think you're right from the SQL standard point of view.
I'm checking with Elevatesoft about the DBISAM implementation
and how to handle the BLOB with calc query.

I'll report back next week.

Jon