fix: wildcard expand + group by doesnt skip expand

[patricebender]

No description provided.

[danjoa]

Suggested change

	const wildcardIndex = column.expand.findIndex(e => e === '*')
	if (wildcardIndex === -1) {
	if (column.expand.includes('*')) {

[danjoa]

Would that mean that:

1. For SELECT Items {*} from Orders group by Items.ID we would not skip the expand?
2. For SELECT Items { ID } from Orders group by Items.ID we would skip the expand?

→ still seems wrong

[danjoa]

As discussed we need to revisit the way we translate OData $apply requests to valid queries, and have those queries translated to native SQL without any assumption of its origin from OData. → bed7329 adds comments to relevant tests about expected valid queries.

[danjoa]

Moreover, and more importantly, we have to ensure that we correctly implement group by, also for things which OData cannot express. In particular, for expands of to-many associations like that:

SELECT from Orders {
   ID, sum (Items.product.price * Items.quantity) as total,
   Items { product.name, quantity }
} group by ID

[patricebender]

As discussed we need to revisit the way we translate OData $apply requests to valid queries, and have those queries translated to native SQL without any assumption of its origin from OData. → bed7329 adds comments to relevant tests about expected valid queries.

Agree 👍

Moreover, and more importantly, we have to ensure that we correctly implement group by, also for things which OData cannot express. In particular, for expands of to-many associations like that:

SELECT from Orders {
   ID, sum (Items.product.price * Items.quantity) as total,
   Items { product.name, quantity }
} group by ID

Also agree, however I would make vote for a two step approach:

1. revert changes in db-service which implemented OData stuff on cqn transformation level, to be OData agnostic again → coordinate with runtime to make the OData adapter come up with a proper CQN which is then transformed as usual.
2. Come up with a plan to implement group by, which also depends on the actual DB-Driver we are talking to