Re: [teiid-designer-dev] Materialized Views

I agree, the right thing to do is make the metamodel change. It would help with refactoring (on your delete example). As far as your side-note, the "Refactoring" framework in Designer has always been "weak" at best. We've always envisioned a framework that allowed "Preview the Changes" similar to what Java/Eclipse. In some cases, of course, we'll need user-interaction to make decisions and can't be derived. Barry ----- Original Message ----- From: "John Verhaeg" <jverhaeg(a)redhat.com&gt; To: "Barry Lafond" <blafond(a)redhat.com&gt; Cc: "teiid-designer-dev" <teiid-designer-dev(a)lists.jboss.org&gt; Sent: Tuesday, July 13, 2010 2:21:57 PM GMT -06:00 US/Canada Central Subject: Re: [teiid-designer-dev] Materialized Views On Jul 13, 2010, at 2:06 PM, Barry Lafond wrote: Would the Materialized Physical table be just an "EReference of somekind? Seems like it since it'll be "external" to the virtual model. Yes, it would be an external reference, but I'm not sure what your point is about it being external. Local and External references aren't really treated much differently. You've hacked before JPAV.... what would it take? :) I didn't say it's easy, just that it should be done. It's definitely too difficult to explain in an e-mail. If you can't figure it out from similar past changes made to metamodels (such as the recent changes to the XML Document metamodel), then I hopefully will have some time next week to take a look. The solution I have locally now would just have to tweak the get/set methods on the virtual table. But have you taken into account what happens when a materialized model gets deleted, either from the workspace or the VDB? As an aside, there might also be something we need to address regarding renames, for any type of model, not just materialization models. Seems like if there is a corresponding model in one or more VDBs, we ought to ask the user whether they want to rename the models within those, too. Impact would be we'd need to create a new VDB instance for all VDBs in the workspace during a rename to query their contents. JPAV