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
OPENJSON currently doesn't allow projecting out the index of elements in the JSON array ("array element identity"), when the WITH clause is used. This feature does exist in Synapse (docs), but not in any other version.
As a result, we currently identify OPENJSON usages where ordering matters, and rewrite them to OPENJSON without WITH, which is less efficient, doesn't support all types (e.g. varbinary can't be used because casting from base64 string data isn't supported), and adds complexity. On the SQL Server side, bringing over array element identity is planned - switch to that when that's done.
The text was updated successfully, but these errors were encountered:
OPENJSON currently doesn't allow projecting out the index of elements in the JSON array ("array element identity"), when the WITH clause is used. This feature does exist in Synapse (docs), but not in any other version.
As a result, we currently identify OPENJSON usages where ordering matters, and rewrite them to OPENJSON without WITH, which is less efficient, doesn't support all types (e.g. varbinary can't be used because casting from base64 string data isn't supported), and adds complexity. On the SQL Server side, bringing over array element identity is planned - switch to that when that's done.
The text was updated successfully, but these errors were encountered: