Document support for ALTER TABLE SET PROPERTIES

[jhlodin]

Description

ALTER TABLE SET PROPERTIES has been supported for a while, but has been missing practical details such as detailed examples, use of the DEFAULT keyword, and what connectors (don't) support it.

General information

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Documentation

How would you describe this change to a non-technical end user or system administrator?

Further document support and use of ALTER TABLE SET PROPERTIES

Related issues, pull requests, and links

• Fixes Document ALTER TABLE SET PROPERTIES #10936
• Some details gathered from Document ALTER MATERIALIZED VIEW/TABLE ... SET PROPERTIES #10774
• Follow up to Document ALTER MATERIALIZED VIEW SET PROPERTIES #10835 (comment)

Documentation

( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`5678`)

[Ordinant]

The interaction between pure SQL role granting and access control role granting is ... unexplored.

[jhlodin]

Understood, but ultimately out of scope for this PR. If someone has input then I can file a follow-up issue

[hashhar]

@Ordinant Do you mean using things like file-based access control together with SQL based access control?

If so such a configuration can never be possible since Trino only allows a single type of system access control to be available at a time.

However connectors may provide their own - and the rule there is that system level configuration wins over connector specific ones.

[Ordinant]

Approved, with quibbles. The ticket probably should be titled "Document lack of support for ..."

[hashhar]

cc: @joshthoward for technical correctness

[rosewms]

LGTM pending comments

[jhlodin]

Discussed with @electrum and agreed that it's probably too granular to devote a sub-section to connector pages that says ALTER TABLE ... SET PROPERTIES is unsupported, especially because the error message is explicit enough about not supporting changing table properties. Removed the "unsupported" fragment and just leaving the core documentation of the clause.

[jhlodin]

@electrum Can we merge this?