generateChangeLog returns tables created by Materialized Views as standard tables

Description

SUMMARY

When I run generateChangeLog to seed my Liquibase project, tables created by materialized views are being returned in the resulting change log.

TO REPRODUCE

  1. Use the attached bookshop.sql to create the testable schema (assumes schema name is "BOOKSHOP_DEV")

  2. Use Liquibase 3.1 to perform generateChangeLog against the schema

EXPECTED RESULTS

The materialized view object "MVIEW_ORDERS" should not be present in a createTable change set.

ACTUAL RESULTS

"MVIEW_ORDERS" is present in a createTable refactoring.

NOTES

It would be nice if Liquibase could filter out tables that are the created by materialized views because I rely on the Materialized View to create/manage these objects.

Environment

DBMS: Oracle 11g on CentOS 6
CLIENT: Windows 7 x64, Java 7

Status

Assignee

Unassigned

Reporter

Peter Pickerill

Labels

None

Fix versions

Affects versions

3.1.0

Priority

Major