Aias00 opened a new issue, #6694: URL: https://github.com/apache/shenyu/issues/6694
- severity: Medium - files: `selector-sqlmap.xml:209-214`; `rule-sqlmap.xml:156-161`; `app-auth-sqlmap.xml:140-145,147-152`; `plugin-sqlmap.xml:136-140,142-146`; `role-sqlmap.xml:79-84`; `auth-path-sqlmap.xml:84-96`; `data-permission-sqlmap.xml:112-117`; `meta-data-sqlmap.xml:165-170`; `namespace-plugin-rel-sqlmap.xml:43-47`; `tag-sqlmap.xml:41-46`; etc. - description: Dozens of `existed`/`*Existed` probes use `SELECT true FROM t WHERE ... LIMIT 1` returning `java.lang.Boolean`. `LIMIT 1` is invalid on Oracle (needs `ROWNUM`/`FETCH FIRST`) and `SELECT true` is not valid Oracle SQL (Oracle has no boolean type). Only `plugin` and `operation-record-log` carry `databaseId="oracle"` variants; none of these `existed` statements do. - impact: Any `existed`/uniqueness probe throws on Oracle; the few Oracle-specific overrides show Oracle is a supported target. - suggested_fix: Standardize on `SELECT 1 FROM ... WHERE ... LIMIT 1` (or `FETCH FIRST 1 ROWS ONLY`) and add `databaseId="oracle"` variants. - confidence: Medium - related_existing: partially overlaps #6161 (Oracle schema DDL) and #5631 (Oracle rule-sqlmap `;`), but this is a distinct, broad mapper-SQL portability defect across the `existed` family. --- _Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/06-medium-tiers.md`](docs/scan2-2026-08-02/06-medium-tiers.md)._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
