"How do I implement the restrict to 0,3?"
This requires an assertion, which is defined in the SQL standard but not implemented in Oracle. (Although there are moves to have them introduced).
What you can do is use a materialized view to enforce it transparently.
create materialized view project_manager
refresh on commit
as
select Project_manager_employee_id
, count(*) as no_of_projects
from project
group by Project_manager_employee_id
/
The magic is:
alter table project_manager
add constraint project_manager_limit_ck check
( no_of_projects <= 3 )
/
This check constraint will prevent the materialized view being refreshed if the count of projects for a manager exceeds three, which failure will cause the triggering insert or update to fail. Admittedly it's not elegant.
Because the mview is refreshed on commit (i.e. transactionally) you will need to build a log on project
table:
create materialized view log on project
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…