You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially reported by @glenworrall
Colin reproduced this. Steps:
The first time I ran it I got ‘partitionName’ as the first column header. Every time after that I got ‘ELEM_PARTITION_PARAM’ as the column header and it was used as the access string shown below.
To try to reproduce I went back one changeset to #67. When I ran the same query I got partitionName and levelName on the first run and then it went to ELEM_PARTITION_PARAM AND FAMILY_LEVEL_PARAM on subsequent runs.
I was able to get the following query to get the wrong label in the second column:
SELECT banana, apple
FROM (
SELECT a AS banana, b AS apple
FROM (
SELECT $->CodeValue AS a, $->UserLabel AS b FROMbis.GeometricElement3d
) AS letters
) AS fruit
If I changed the query slightly e.g. fruit->fruity then it went back. The metadata changed from:
Initially reported by @glenworrall
Colin reproduced this. Steps:
The first time I ran it I got ‘partitionName’ as the first column header. Every time after that I got ‘ELEM_PARTITION_PARAM’ as the column header and it was used as the access string shown below.
To try to reproduce I went back one changeset to #67. When I ran the same query I got partitionName and levelName on the first run and then it went to ELEM_PARTITION_PARAM AND FAMILY_LEVEL_PARAM on subsequent runs.
I was able to get the following query to get the wrong label in the second column:
If I changed the query slightly e.g. fruit->fruity then it went back. The metadata changed from:
to
So it seems like it has something to do with caching of the sql statement.
The text was updated successfully, but these errors were encountered: