Red Hat Bugzilla – Bug 112160
oracle-se test sql scripts are being sourced when running unit tests under postgres
Last modified: 2007-04-18 13:00:12 EDT
XVersioningSuite current has 5 errors when run with PostgreSQL on the
6.0 branch. The problem seems to stem from the fact that wrong
auto-generated .sql scripts are being sourced. Specificically,
oracle-se scripts with Oracle-specific data types, such as CLOB and
BLOB, are being sourced and causing the unit test setup phase to fail.
Here's what I'm getting:
2003-12-15 10:06:37,344 [ main] WARN installer.LoadSQLPlusScript - Loading: '/var/ccm-devel/dev/vadim/60/core/build/tests/sql/oracle-se/com/arsdigita/versioning/setup.sql'
2003-12-15 10:06:37,382 [ main] WARN installer.LoadSQLPlusScript - Relative path found: 'create.sql'
2003-12-15 10:06:42,281 [ main] WARN installer.LoadSQLPlusScript - Relative path found: 'table-te_vt1-auto.sql'
2003-12-15 10:06:42,281 [ main] WARN installer.LoadSQLPlusScript - Recursively including: '/var/ccm-devel/dev/vadim/60/core/build/tests/sql/oracle-se/com/arsdigita/versioning/table-te_vt1-auto.sql'
2003-12-15 10:06:42,287 [ main] ERROR installer.LoadSQLPlusScript - -- FAILED: ERROR: Type "clob" does not exist
2003-12-15 10:06:42,287 [ main] ERROR installer.LoadSQLPlusScript - SQL: create table te_vt1 (
id INTEGER not null
This is preventing merge of change 38778 (see bug #101749).
I should've realized on friday: while this is a bug, it is a known
one. The build.tests.sql.dir.db property in build.xml defaults to oracle:
On autotester, 'oracle-se' is replaced by a database.key property in
ant.properties that can be switched from oracle to postgres.
Changing in my local checkout fixes the test failures.
With this out of the way, can you finish bug #101749?
I don't have write permissions on the 6.0 branch.