feat: dbeaver mysql compatibility, use statement and information_schema.tables

[sunng87]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

This patch is to resolve compatibility issues with dbeaver client:

• it tries to access some field like data_size in information_schema.tables
• it uses use statement instead of modern use command which most other clients use

This patch fills these two gaps and make dbeaver client works for most cases. There is another statement to be supported: SHOW TABLE STATUS FROM public LIKE 'system_metrics' but it's not a blocking issue for our scenario. SHOW TABLE STATUS is tracked in #3354

This patch brings back USE statement support in #2022 as we finally found a real use-case for it. And it also makes current_schema modifiable and propagate to Session.

The data fields of information_schema.TABLES in this patch are all for placeholder. I haven't fill real data into these fields. TODO item is left to future enhancement.

Future work

I'm going refactor Session and QueryContext to use Arc<RwLock<>> for all modifiable fields, like time-zone, schema. This makes the change automatically propagate from QueryContext to Session. The idea of QueryContext::update_session is smart, but it's going to be difficult to maintain in future.

Checklist

• [ ] I have written the necessary rustdoc comments.
• [ ] I have added the necessary unit tests and integration tests.
• [ ] This PR requires documentation updates.

Summary by CodeRabbit

• New Features

  • Introduced new columns (data_length, max_data_length, index_length, avg_row_length) in the information_schema tables for enhanced data insight.
  • Enhanced query result structure with additional relevant columns for better data representation.

• Improvements

  • Implemented custom display formatting for TableOptions to improve readability.

• Tests

  • Added tests to verify the string conversion of TableOptions ensuring accurate display.

• Bug Fixes

  • Corrected column arrangement in query results to ensure consistency and correctness.

[coderabbitai[bot]]

Walkthrough

The changes introduce new columns (data_length, index_length, max_data_length, and avg_row_length) to the information_schema tables in a database system. These modifications also involve updating related data structures, implementing display formatting for TableOptions, and adjusting test outputs to reflect the new schema.

Changes

File	Change Summary
src/.../tables.rs	Added constants and fields for new columns in information_schema along with vector builders.
src/table/src/requests.rs	Implemented fmt::Display for TableOptions and added tests for string conversion.
tests/.../information_schema.result	Updated test results for information_schema tables to include new columns.
tests/.../create.result	Updated output format in test results to include new columns in query results.

Sequence Diagram(s)

None generated.

Poem

In coders' realm, where data gleams,
New columns rise to fulfill dreams,
Length and index, data's tale,
With tests aligned, they set the sail,
Options display in string's embrace,
Schema's wonder, a data chase.

---

[!TIP]

Early access features: enabled

We are currently testing the following features in early access: - **OpenAI `gpt-4o` model for code reviews and chat**: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available. Note: - You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file. - Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide feedback and report issues. - OSS projects are currently opted into early access features by default.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 78.97196% with 45 lines in your changes missing coverage. Please review.

Project coverage is 84.55%. Comparing base (df0fff2) to head (12157b4). Report is 18 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #4218 +/- ## ========================================== - Coverage 84.84% 84.55% -0.29% ========================================== Files 1041 1049 +8 Lines 183028 186483 +3455 ========================================== + Hits 155291 157683 +2392 - Misses 27737 28800 +1063 ```

[killme2008]

I'm going refactor Session and QueryContext to use Arc<RwLock<>> for all modifiable fields, like time-zone, schema. This > makes the change automatically propagate from QueryContext to Session. The idea of QueryContext::update_session is > smart, but it's going to be difficult to maintain in future.

It may hurt performance, must be careful or do some benchmark.

[killme2008]

There are many columns in tables, see https://dev.mysql.com/doc/refman/8.4/en/information-schema-tables-table.html

I believe we should consider including all placeholders at this time.

[sunng87]

It may hurt performance, must be careful or do some benchmark.

Should be ok because these data are all associated with a single database connection. Actually there is no concurrent access at all. Using locks is just to bypass rust compiler check.

[killme2008]

@evenyag @fengjiachun Please take a look.

[sunng87]

@evenyag just updated, please check again