Is there a way to make the modeler ignore existing DB tables that I don't want it to touch, during reverse engineering and (especially) migration? I have a unique business constraint that requires me to create a schema within an existing database, even though the new tables have no relationships with the existing ones. If I make a schema change within the modeler, it wants to drop all of the tables Cayenne doesn't know about, and I have to manually scan and ignore these entries.
-- Thanks, Tad Fisher
