View Revisions: Issue #6945
| Summary | 0006945: Add overrides for isBlob and isClob for AseDatabasePlatform | ||
|---|---|---|---|
| Revision | 2025-06-16 16:08 by cquamme | ||
| Additional Information | |||
| Revision | 2025-06-16 16:09 by cquamme | ||
| Additional Information | Introduced in issue 0006674 | ||
| Revision | 2025-06-16 16:08 by cquamme | ||
| Description | Currently AseDatabasePlatform is using AbstractDatabasePlatforms isBlob and isClob method, which uses column.getMappedType() to determine if it is a blob or clob. We should add an override, because this causes issues for univarchar types. Column [name=colName; jdbcType=univarchar; mappedType=LONGVARBINARY] |
||
| Revision | 2025-06-16 16:16 by cquamme | ||
| Description | Currently AseDatabasePlatform is using AbstractDatabasePlatforms isBlob and isClob method, which uses column.getMappedType() to determine if it is a blob or clob. We should add an override, because this causes issues for univarchar types. It should use column.getJdbcType(), as it did previously. Column [name=colName; jdbcType=univarchar; mappedType=LONGVARBINARY] |
||
| Revision | 2025-06-16 16:16 by cquamme | ||
| Description | Currently AseDatabasePlatform is using AbstractDatabasePlatforms isBlob and isClob method, which uses column.getMappedType() to determine if it is a blob or clob. We should add an override, because this causes issues for univarchar types. It should use column.getJdbcTypeCode(), as it did previously. Column [name=colName; jdbcType=univarchar; mappedType=LONGVARBINARY] |
||
| Revision | 2025-06-16 16:08 by cquamme | ||
| Steps To Reproduce | |||
| Revision | 2025-06-16 16:51 by cquamme | ||
| Steps To Reproduce | 1. Setup Postgres -> Sybase 2. Have a table with a primary key that is a UNIVARCHAR on the Sybase side 3. Do an update on Postgres side with "All SQL Statement" logging on, and notice that the update will not the UNIVARCHAR PK on the update for Sybase. |
||
| Revision | 2025-06-16 16:52 by cquamme | ||
| Steps To Reproduce | 1. Setup Postgres -> Sybase ASE 2. Have a table with a primary key that is a UNIVARCHAR on the Sybase side 3. Do an update on Postgres side with "All SQL Statement" logging on, and notice that the update will not the UNIVARCHAR PK on the update for Sybase. |
||
| Revision | 2025-06-18 12:30 by cquamme | ||
| Description | Currently AseDatabasePlatform is using AbstractDatabasePlatforms isBlob and isClob method, which uses column.getMappedType() to determine if it is a blob or clob. We should add an override, because this causes issues for univarchar types. It should use column.getJdbcTypeCode(), as it did previously. Column [name=colName; jdbcType=univarchar; mappedType=LONGVARBINARY] We should also add a unit test case for AseDatabasePlatform, specifically around the canColumnBeUsedInWhereClause() method where this error occurred. |
||
| Revision | 2025-06-18 12:31 by cquamme | ||
| Description | Currently AseDatabasePlatform is using AbstractDatabasePlatforms isBlob and isClob method, which uses column.getMappedType() to determine if it is a blob or clob. We should add an override, because this causes issues for univarchar types. It should use column.getJdbcTypeCode(), as it did previously. Column [name=colName; jdbcType=univarchar; mappedType=LONGVARBINARY] We should also add a unit test class for AseDatabasePlatform, specifically around the canColumnBeUsedInWhereClause() method where this error occurred. |
||