bug(oceanbase-oracle): COMMENT DDL doubles backslashes (regression vs base Oracle)

[Aias00]

Description

OceanbaseOracleMetaData.tableDDL builds COMMENT ON ... IS using EasyStringUtils.escapeAndQuoteString(comment), which doubles both ' and \. The base OracleMetaData correctly uses OracleIdentifierProcessor.quoteStringLiteral (only doubles '), and OceanBase Oracle mode treats \ as a literal character (OceanbaseOracleIdentifierProcessor extends OracleIdentifierProcessor without overriding escape). So a comment containing \ (Windows paths, regex) is regenerated as \\ and persisted corrupted when the DDL is re-applied.

Location

chat2db-community-plugins/chat2db-community-oceanbase-oracle/.../OceanbaseOracleMetaData.java:52,64 (tableComment, columnComment). Base OracleMetaData uses quoteStringLiteral; OracleIdentifierProcessor.quoteStringLiteral only doubles '.

Impact

Comments containing backslashes are persisted as doubled-backslash when the regenerated DDL is executed.

Suggested fix

Use OceanbaseOracleIdentifierProcessor.INSTANCE.quoteStringLiteral(comment) (dialect-correct, only escapes '), mirroring the base OracleMetaData.

Related existing

None.

[github-actions]

Thanks for pinpointing the OceanBase Oracle-mode DDL escaping difference: regenerated COMMENT ON ... IS statements appear to double backslashes, so reapplying the DDL changes stored comments.

To let a maintainer verify this against the current database bug form, please add the missing required details: Chat2DB edition and version, deployment type, operating system and version, OceanBase version, impact/scope, and workaround status. Most importantly, provide a minimal sanitized table/comment example plus the exact steps and resulting generated DDL showing one backslash becoming two.

``

Generated by AI Issue Assistant for #2428 · 6.35 AIC · ⌖ 2.69 AIC · ⊞ 16.4K · ◷