[OceanBase] Materialized views are missing from schema and SELECT fails with masking resource-not-found error

Provide the Bytebase version you are using

3.22.0

Describe the bug

When Bytebase connects to OceanBase 4.3.5, materialized views are not shown in the database schema browser.

Running a direct SELECT against an existing materialized view also fails in Bytebase with the following error (database and object names redacted):

internal: failed to mask data: resource not found: database: <redacted>, schema: , table: <redacted_materialized_view>

The same materialized view is displayed correctly in DBeaver and can be queried successfully there. Navicat does not list the materialized view separately in its object browser, but the same SELECT query still succeeds.

This suggests that Bytebase does not discover or classify OceanBase materialized views correctly, and the data-masking/resource lookup path then treats the materialized view as a missing table.

Steps to reproduce

1. Connect Bytebase 3.22.0 to an OceanBase 4.3.5 instance containing a materialized view.
2. Open the corresponding database/schema in Bytebase.
3. Observe that the materialized view is not listed in the schema browser.
4. Open the SQL editor and run:
   sql复制

   SELECT * FROM <materialized_view>;

5. Observe the failed to mask data: resource not found error.
6. Run the same query with the same database account in DBeaver or Navicat and observe that it succeeds.

Expected behavior

• OceanBase materialized views should be discovered and displayed in the schema browser.
• Direct SELECT queries against existing materialized views should execute successfully.
• If data masking applies, Bytebase should resolve the materialized view metadata correctly instead of reporting it as a missing table.

Provide the database you are using

OceanBase 4.3.5

Additional context

• DBeaver displays the materialized view and queries it successfully.
• Navicat may not display the materialized view separately, but queries it successfully.
• Database, schema, and object names have been redacted from the error message for privacy.