[JCR-1362] DatabaseJournal improperly finds tables in external schemas when used on Oracle

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.3, 1.4
• Fix Version/s: core 1.4.6
• Component/s: jackrabbit-core, sql
• Assignee: Unassigned
• Reporter: Chris Schmidt
• Created: 06/Feb/08 01:06
• Updated: 19/Nov/09 13:13
• Resolved: 18/Aug/08 07:41

Description

The DatabaseJournal currently calls database metadata to determine if the journal table has already been created. It uses the following code to do so:

ResultSet rs = metaData.getTables(null, null, tableName, null);

The Oracle driver sometimes will return the table if it is in another schema on the same database. Other DBMS code within JackRabbit has a specific Oracle version that handles this case. In order for the journal table to be properly created, Oracle databases will need the schema name included in the getTables() call.