Sensitive views using joins as part of the WHERE clause but not having any of the joined columns as part of the result set would be really nifty. Any chance?

EG

SELECT Companies.*
FROM Companies
JOIN Career ON Career._fkCompanies = _ID



Roy Lambert

Roy,

<< Sensitive views using joins as part of the WHERE clause but not having
any of the joined columns as part of the
result set would be really nifty. Any chance? >>

Views already act like tables in that they reflect changes in the underlying
tables and can be refreshed, etc.  The only part that they don't do is
updating, which is something that I'm working on fixing in a future release
with something like INSTEAD OF triggers on view INSERT, UPDATE, or DELETE
operations.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Views already act like tables in that they reflect changes in the underlying
>tables and can be refreshed, etc. The only part that they don't do is
>updating, which is something that I'm working on fixing in a future release
>with something like INSTEAD OF triggers on view INSERT, UPDATE, or DELETE
>operations.

I was hoping to be just able to use a table component.....

Roy Lambert

Roy,

<< I was hoping to be just able to use a table component..... >>

You *can* use a TEDBTable component to open any view.   The only problem is
that, right now, you can't update any views that can't return a sensitive
(in the TEDBQuery sense) result set.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>You *can* use a TEDBTable component to open any view.

Figured that one out already

>The only problem is
>that, right now, you can't update any views that can't return a sensitive
>(in the TEDBQuery sense) result set.

This is what prompted my original question. The one about table components was prompted by "The only part that they don't do is
updating, which is something that I'm working on fixing in a future release with something like INSTEAD OF triggers" which makes me think Query.

Roy Lambert