Comments on: Finding Wrong Hints https://www.salvis.com/blog/2022/01/14/finding-wrong-hints/ Database-centric development Mon, 20 Nov 2023 10:47:27 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Philipp Salvisberg https://www.salvis.com/blog/2022/01/14/finding-wrong-hints/#comment-116137 Mon, 20 Nov 2023 10:47:27 +0000 https://www.salvis.com/blog/?p=11443#comment-116137 In reply to Pantea Tourang.

Thank you, Pantea.

]]> By: Pantea Tourang https://www.salvis.com/blog/2022/01/14/finding-wrong-hints/#comment-116131 Mon, 20 Nov 2023 07:58:40 +0000 https://www.salvis.com/blog/?p=11443#comment-116131 Very informative article. I learned new stuff. Thank you

]]> By: Philipp Salvisberg https://www.salvis.com/blog/2022/01/14/finding-wrong-hints/#comment-93677 Mon, 17 Jan 2022 15:36:08 +0000 https://www.salvis.com/blog/?p=11443#comment-93677 In reply to Jonathan Lewis.

An important remark. Thank you.

The checks regarding “G-9602: Always use the alias name instead of the table name” are applied only for chosen hints (e.g. leading). table_stats, index_stats and column_stats are not among them. For these three hints only the name is checked. However, based on your comment I create two issues on the custom validator GitHub repo:

BTW: @query_block references are currently not checked. This is a known and documented limitation and might lead to some false negatives.

]]>