microsoft/Kusto-Query-Language

alter row_level_security with db prefix

vplauzon opened this issue · 2 comments

The following script:

.alter table mydb.mytable policy row_level_security enable "MyFunction"

is parsed as an alter update policy (command kind).

Same occur if there is a cluster + db prefix.

That is legal when ran in Web UI.

It seems the potential database prefix was taken into account.

I see similar behaviour with

.alter table mydb.mytable policy ingestiontime true

Version 11.5.6 now has fixes for commands that allowed for db.entity pattern.