Triggers: For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account. Assume that the database system uses immediate binding for rule execution. Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”. The active rules for this insertion are given below – define trigger insert into_branch_cust_via_depositor after insert on depositor referencing new table as inserted for each statement insert into branch_cust select branch_name, customer_name from inserted, account where inserted.account_number = account.account_number define trigger insert into branch cust via account after insert on account referencing new table as inserted for each statement insert into branch cust select branch name, customer name from depositor, inserted where depositor.account number = inserted.account number In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Question

Want to see the full answer?

Answer 1

Expert Solution & Answer

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Expert Solution & Answer

Want to see the full answer?

Check out a sample textbook solution

See solution

Answer 2

Expert Solution & Answer

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Expert Solution & Answer

Want to see the full answer?

Check out a sample textbook solution

See solution

Answer 3

Expert Solution & Answer

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Expert Solution & Answer

Want to see the full answer?

Check out a sample textbook solution

See solution

Answer 4

Expert Solution & Answer

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Expert Solution & Answer

Want to see the full answer?

Check out a sample textbook solution

See solution

Answer 5

Expert Solution & Answer

Answer 6

Expert Solution & Answer

Answer 7

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Answer 8

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Answer 9

Chapter 5, Problem 6PE

Explanation of Solution

Triggers:

For inserting into the materialized view branch_cust the user must set a database trigger on an insert into depositor and account.

Assume that the database system uses immediate binding for rule execution.

Further, assume that the current version of a relation is denoted by the relation name itself, while the set of newly inserted tuples is denoted by qualifying the relation name with prefix “inserted”.

The active rules for this insertion are given below –

define trigger insert into_branch_cust_via_depositor

after insert on depositor

referencing new table as inserted for each statement

insert into branch_cust

select branch_name, customer_name

from inserted, account

where inserted.account_number = account.account_number

define trigger insert into branch cust via account

after insert on account

referencing new table as inserted for each statement

insert into branch cust

select branch name, customer name

from depositor, inserted

where depositor.account number = inserted.account number

In the above statements, if the execution binding was deferred (instead of immediate), then the result of the join of the set of new tuples of account with the set of new tuples of depositor would have been inserted by both active rules, leading to duplication of the corresponding tuples in branch_cust...

Answer 10

Expert Solution & Answer

Answer 11

Expert Solution & Answer

Answer 12

Want to see the full answer?

Check out a sample textbook solution

See solution

Answer 13

Ch. 5 - Prob. 1PE Ch. 5 - Prob. 2PE Ch. 5 - Prob. 4PE Ch. 5 - Prob. 5PE Ch. 5 - Consider the bank database of Figure 5.21. Let us...Ch. 5 - Prob. 7PE Ch. 5 - Prob. 8PE Ch. 5 - Prob. 9PE Ch. 5 - Using the relation from Exercise 5.9, write an...Ch. 5 - Show how to express group by cube(a, b, c, d)...

Concept explainers

Videos

Explanation of Solution

Want to see the full answer?

Chapter 5 Solutions