Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Allow sensitive views to be included in a transaction
Mon, Mar 31 2014 3:40 PMPermanent Link

Barry

I have sensitive views that I'd like to be able to include in transactions.

But if I try to use the view name in a Start Transaction .. statement, I get "Error 401 The table "MyView" does not exist in schema default".

To get around this, I need to extract the table name from the view definition and then start the transaction on the underlying table. (The view can be created dynamically and the table name in the view can change. So it is much easier for me to refer to it as the view name, not the table name)

It would be easier if EDB could figure out the table that makes up the sensitive view so I can include the view name in the transaction.

Barry
v2.13B2
Wed, Apr 2 2014 7:06 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Barry,

<< I have sensitive views that I'd like to be able to include in
transactions. >>

I don't know about this one.  On the one hand, it's easy to do, but could
really trip someone up if they're not careful.

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Apr 3 2014 3:33 PMPermanent Link

Barry

"Tim Young [Elevate Software]" wrote:

Barry,

<< I have sensitive views that I'd like to be able to include in
transactions. >>

<I don't know about this one.  On the one hand, it's easy to do, but could
really trip someone up if they're not careful.>

How could it trip someone up?
An sensitive view still has to be a single table. Are you thinking someone might put the view *and* the underlying table in the same transaction? If so, just ignore the second reference.

Barry
Thu, Apr 3 2014 4:10 PMPermanent Link

Raul

Team Elevate Team Elevate

On 4/3/2014 3:33 PM, Barry wrote:
>
> How could it trip someone up?
> An sensitive view still has to be a single table.

Not sure about implications but you can have query with sub-queries and
still be sensitive so there are cases of more than 1 table possible
(both/all tables would get updated i believe if you edit and post).

Raul
Thu, Apr 3 2014 11:13 PMPermanent Link

Barry

Raul wrote:

On 4/3/2014 3:33 PM, Barry wrote:
>>
>> How could it trip someone up?
>> An sensitive view still has to be a single table.

<
Not sure about implications but you can have query with sub-queries and
still be sensitive so there are cases of more than 1 table possible
(both/all tables would get updated i believe if you edit and post).>

Actually my view does use a subquery in the Where clause. But since only the driving table is sensitive, there is no reason to include the other tables (that make up the sensitive view) in the transaction because they are insensitive.

Or am I missing something here?

Barry
Image