Re: [teiid-designer-dev] Potential Designer Source Bindings Strategy
On Mar 25, 2010, at 10:27 AM, Ramesh Reddy wrote:
I am not sure why you guys are hung up on multiple Teiid instance
usecase. This is not the scenario 90% of the times. IMO, preview should
be done from single Teiid instance, preferably that is local. For the
execution of VDB in DTP you can connect to any Teiid instance of your
choice. This makes things lot simpler!
I think all of us are also envisioning the "normal" use case to involve only one
Teiid for preview, but at the same time I see no reason to enforce this as a rule. The
only extra complexity involved in allowing for more than one is if we're doing things
automatically using hidden VDBs, especially if the preview Teiid is being shared amongst
several users, which we've been told is a very likely case. That's a good part of
the reason I'm suggesting we eliminate the idea of having anything hidden.
I see not much value; source queries are sent directly to source
through
Teiid. It would be no different, unless you are letting users type the
SQL, in which case they can use certain functions that are not supported
by the source and evaluated by the Teiid. We do not let uses type in SQL
for preview, so no issue. They could always use DTP or Squirrel to do
that.
Ah, you're correct Ramesh, I'm mixing test execution with preview. My bad, never
mind.
Thanks,
JPAV