order by sub stmt support db.table.col

[TCeason]

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

order by sub stmt support db.table.col.

In this pr just support db.table.col not do any judge for db_name and table_name.

because the struct ColumnBinding does not have database_name.

#[derive(Clone, PartialEq, Debug)]
pub struct ColumnBinding {
    /// Table name of this `ColumnBinding` in current context
    pub table_name: Option<String>,
    /// Column name of this `ColumnBinding` in current context
    pub column_name: String,
    /// Column index of ColumnBinding
    pub index: IndexType,

    pub data_type: DataTypeImpl,

    /// Consider the sql: `select * from t join t1 using(a)`.
    /// The result should only contain one `a` column.
    /// So we need make `t.a` or `t1.a` invisible in unqualified wildcard.
    pub visible_in_unqualified_wildcard: bool,
}

And actually I'm not sure this issue can be fixed as this pr.

In my mind it's better fixed with ISSUE #6080

Changelog

• New Feature

Related Issues

Fixes #6192

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
databend	⬜️ Ignored (Inspect)		Jun 27, 2022 at 4:20AM (UTC)

[mergify]

Thanks for the contribution!
I have applied any labels matching special text in your PR Changelog.

Please review the labels and make any necessary changes.

[TCeason]

Here, we need an error, but now it will succeed. I will create a new ISSUE.

'root'@mysqldb 17:57:14 [(none)]> SELECT DISTINCT(id) FROM a.t ORDER BY a.t.id2;
ERROR 1105 (HY000): Code: 1065, displayText = error: 
  --> SQL:1:39
  |
1 | SELECT DISTINCT(id) FROM a.t ORDER BY a.t.id2
  |                                       ^^^^^^^ for SELECT DISTINCT, ORDER BY expressions must appear in select list

[TCeason]

wait pr https://github.com/datafuselabs/databend/pull/6219/files merged

[BohuTANG]

#6219 merged

[TCeason]

Note: the test in this pr needs to enable planner v2 but now we do not support cluster execute, so skip it.

[TCeason]

09_0008_fuse_optimize_table:                                            [ FAIL ] - result differs with:
--- /workspace/tests/suites/0_stateless/09_fuse_engine/09_0008_fuse_optimize_table.result	2022-06-27 04:37:36.977439331 +0000
+++ /workspace/tests/suites/0_stateless/09_fuse_engine/09_0008_fuse_optimize_table.stdout	2022-06-27 04:41:30.575939379 +0000
@@ -23,9 +23,3 @@
 9
 10
 1
-5
-6
-7
-8
-9
-10

Maybe that's a flaky test?