2 foreign keys in a table

Hi!
We just started to develop in jDeveloper 9.0.3. and we are pretty in the beginning of it. However, we have a strict deadline and we have to produce something. Please, could anybody help in the following issue?
We want to insert new records into a Working_hours table, which has two foreign keys, Person_id and Projekt_id. We want the user only see (his own) Person_name and all the Project_name-s from the corresponding tables. How can we solve this in the Application Module? It is better to make View Links between three View Objects, or just create only one View Object?
Besides, we want the user to choose a Project_name from a drop-down list (InputSelect). How to do this in a Struts based JSP application?
Thanks a lot!

Hi
Refer to following links
<b>http://help.sap.com/saphelp_47x200/helpdata/en/1f/29ef5777df11d2959800a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/1f/29ef5777df11d2959800a0c929b3c3/frameset.htm
Search Help Topic
http://help.sap.com/saphelp_erp2005/helpdata/en/cf/21ee45446011d189700000e8322d00/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/1f/29ef5777df11d2959800a0c929b3c3/frameset.htm</b>
Hope this will help.
Please reward suitable points.
Regards
- Atul

Similar Messages

Delete a user from a table whose name is a foreign key in other tables

Dear All;
I am trying to figure out an easy way to do this. I just recently took someone application who utilized 500 tables. I am trying to delete a user from a table called member_table. However, I am having problems doing so because the user name is a foreign key in other tables which has a relationship with this member_table. I really can't naviagte through all 500 different tables and start deleting the user from each table . hence, I would like to figure out a way to delete the user from the member_table without getting the error message
ORA - 02292 "Integrity Constraint (....) violated child record found

Unless you want to find and re-create all of the FK's that point to that field so you can make them ON DELETE CASCADE (note it is the FK not the PK that has that attribute), you will need to either delete that member id from each of the child tables individually or update each one individually to either null or some valid value in member_table before you can delete the id from member_table.
You can find all of the tables, and the corresponding column_name that have an FK relationship to memeber_table with the following:
SELECT c.table_name, col.column_name
FROM user_constraints c, user_cons_columns col
WHERE c.constraint_name = col.constraint_name and
      c.r_constraint_name = (SELECT constraint_name
                             FROM user_constraints
                             WHERE table_name = 'MEMBER_TABLE' and
                                   constraint_type = 'P') and
     c.constraint_type = 'R';If there are a lot of these, you could use something similar to generate the set of delete/update statements that would be needed.
John

FOREIGN KEY CONSTRAINT 의 MASTER TABLE NAME 의 확인

제품 : ORACLE SERVER
작성날짜 : 1995-11-02
FOREIGN KEY CONSTRAINT 의 MASTER TABLE NAME 의 확인
===================================================
다음은 FOREIGN KEY CONSTRAINT 이름으로 REFERENCE 하는 TABLE
(MASTER TABLE)을 찾는 SQL SCRIPT이다.
col Primary_key_table format a20
col Constraint_name format a20
select a.object_name Primary_Key_table,
c.name Constraint_name
from dba_objects a,
sys.cdef$ b,
sys.con$ c
where c.name = 'EMP_FOREIGN_KEY' -- CONSTRAINT NAME
and b.con# = c.con#
and b.robj# = a.object_id
/

The set of constraints as you show it is valid, but will likely result in a lot of violations since both child columns are larger than the parent. The Oracle 2256 error has nothing to do with data validation, nor with the different lengths of the columns. The documentation says
02256, 00000, "number of referencing columns must match referenced columns"
// *Cause: The number of columns in the foreign-key referencing list is not
// equal to the number of columns in the referenced list.
// *Action: Make sure that the referencing columns match the referenced
// columns.Look at the actual statement that the client ran. It will be different than the one you posted. one of the two column lists will have more columns than the other.

FOREIGN KEY CONSTRAINT의 MASTER TABLE을 REFERENCE하는 TABLE 찾기

제품 : SQL*PLUS
작성날짜 : 2003-12-17
FOREIGN KEY CONSTRAINT의 MASTER TABLE을 REFERENCE하는 TABLE 찾기
================================================================
Master table 이 dept2일 때, 이 테이블을 참조하는 table들을 찾는 SQL
select x.table_name "reference table"
from
(select distinct r_constraint_name,table_name
from all_constraints
where constraint_type='R' ) x, all_constraints a
where a.table_name = 'DEPT2'
and x.r_constraint_name = a.constraint_name;

Foreign keys at the table partition level

Anyone know how to create and / or disable a foreign key at the table partition level? I am using Oracle 11.1.0.7.0. Any help is greatly appreciated.

Hmmm. I was under the impression that Oracle usually ignores indices on columns with mostly unique and semi-unique values and prefers to do full-table scans instead on the (questionable) theory that it takes almost as much time to find one or more semi-unique entries in an index with a billion unique values as it does to just scan through three billion fields. Though I tend to classify that design choice in the same category as Microsoft's design decision to start swapping ram out to virtual memory on a PC with a gig of ram and 400 megs of unused physical ram on the twisted theory that it's better to make the user wait while it needlessly thrashes the swapfile NOW than to risk being unable to do it later (apparently, a decision that has its roots in the 4-meg win3.1 era and somehow survived all the way to XP).

Foreign keys to same table / Who columns in User table???

Hi All,
We are designing a database for our client and we are using common columns in all tables like CreatedBy and UpdatedBy which are foreign keys to USER table. My question is can we use these two columns in USER table and have the foreign key constraints to the same tables?
USER table script will look like following..
CREATE TABLE XX_USER
     User_ID                              VARCHAR2(10)
,     CreatedBy                         NUMBER(10)
,     UpdatedBy                         NUMBER(10)
,     User_Name                         VARCHAR2(100)     NOT NULL
,     Designation                         VARCHAR2(100)     NOT NULL
,     CONSTRAINT USER_ISACTIVE_CHECK CHECK (Is_Active in ('Y', 'N'))
,     CONSTRAINT USER_KEY PRIMARY KEY (User_ID),
,     CONSTRAINT USER_CREATED_BY FOREIGN KEY (CREATED_BY)
     REFERENCES XX_USER (USER_ID)
,     CONSTRAINT USER_UPDATED_BY FOREIGN KEY (UPDATED_BY)
     REFERENCES XX_USER (USER_ID)
);I think what I am doing (the above script) is not correct. Could someone please suggest me how can solve this issue?
Thanks in advance,
Oraebs

user8644385 wrote:
We are designing a database for our client and we are using common columns in all tables like CreatedBy and UpdatedBy which are foreign keys to USER table. My question is can we use these two columns in USER table and have the foreign key constraints to the same tables?You can. After fixing synatx errors:
SQL> CREATE TABLE XX_USER
2 (
3   User_ID        VARCHAR2(10)
4 , CreatedBy     NUMBER(10)
5 , UpdatedBy     NUMBER(10)
6 , User_Name     VARCHAR2(100) NOT NULL
7 , Designation   VARCHAR2(100) NOT NULL
8 , Is_Active     VARCHAR2(1)
9 , CONSTRAINT USER_ISACTIVE_CHECK CHECK (Is_Active in ('Y', 'N'))
10 , CONSTRAINT USER_KEY PRIMARY KEY (User_ID)
11 , CONSTRAINT USER_CREATED_BY FOREIGN KEY (CreatedBy)
12       REFERENCES XX_USER(USER_ID)
13 , CONSTRAINT USER_UPDATED_BY FOREIGN KEY (UpdatedBy)
14       REFERENCES XX_USER(USER_ID)
15 )
16 /
Table created.
SQL> Now USER_ID is a string while CreatedBy/UpdatedBy is a number. Even though it is allowed, it limits USER_ID to numeric strings and causes implicit conversions while validating. So I would change CreatedBy/UpdatedBy data type to VARCHAR2(10).
SY.

Update primary key thats also a foreign key in another table

Hi Developers,
I need to update the primary key for a record but it's also the foreign key in another table.
Example,
Table 1 Details
Name : Parent_Table
Columns : ID, Name, Age
Primary Key : ID
Table 2 Details
Name : Child_Table
Columns : ID, Parent_ID, Name, Age
Primary Key : ID
Foreign Key : Parent_ID (Primary Key in Parent_Table)
Parent_Table
ID Name Age
1001 Sam 26
1002 George 25
Child_Table
ID Parent_ID Name Age
1010 1001 Sam 26
1020 1002 George 25
Now I want to update ID (1001) in Parent_table as 2001 and also, I want to update Parent_ID (1001) in Child_Table as 2001.
How we will write the java code to update these columns.
Thanks in advance.

dcminter wrote:
If you're looking at changing the primary keys in your data then there's probably something wrong with your data structure.Depends how you feel about business primary keys versus surrogates. Personally I prefer the latter so I'm with you in theory. In practice, however, a DB that uses a business PK may well find that it's a legitimate use case to change the key value (but then that's why I like surrogates in the first place!)Primary keys should not have meaning.

How to create a foreign key for the table from two different tables?

Hi All,
I have a three table like below. In the below table SAMPLE_CONS_CHECK and SAMPLE_CONS2_CHECK will be having the primary key for NAME column. The same SAMPLE_CONS3_CHECK table also having the primary key for NAME column and forieign key for SAMPLE_CONS_CHECK and SAMPLE_CONS2_CHECK tables. See the below code 2
code 1:
CREATE TABLE SAMPLE_CONS_CHECK
        (NAME VARCHAR2(10),
        SERIES VARCHAR2(5)
CREATE TABLE SAMPLE_CONS2_CHECK
        (NAME VARCHAR2(5),
         MODEL NUMBER
CREATE TABLE SAMPLE_CONS3_CHECK
        (NAME VARCHAR2(5),
         MODEL_NO NUMBER
        )code 2
alter table SAMPLE_CONS_CHECK
add constraint SAMPLE_CONS_CHECK_pk primary key (NAME)
alter table SAMPLE_CONS2_CHECK
add constraint SAMPLE_CONS2_CHECK_pk primary key (NAME)
alter table SAMPLE_CONS3_CHECK
add constraint SAMPLE_CONS3_CHECK_pk primary key (NAME)
ALTER TABLE SAMPLE_CONS3_CHECK ADD
CONSTRAINT SAMPLE_CONS3_CHECK_FK1 FOREIGN KEY
     NAME
) REFERENCES SAMPLE_CONS_CHECK
    NAME
) ON DELETE CASCADE;
ALTER TABLE SAMPLE_CONS3_CHECK ADD
CONSTRAINT SAMPLE_CONS3_CHECK_FK2 FOREIGN KEY
     NAME
) REFERENCES SAMPLE_CONS2_CHECK
    NAME
) ON DELETE CASCADE;From the above schenario i am able to insert the data to SAMPLE_CONS3_CHECK table. But the parent data is already available in the parent table. The problem is here two different constarints from two different tables. While inserting, it is checking from both the tables whether the parent is exist or not.
How can i solve this problem? Can anyone halp me about this?
Thanks
Edited by: orasuriya on Aug 8, 2009 2:02 AM

Actually the design is completely incorrect.
What you say is
I have
'foo', 'foo series'
'foo','foo model'
'foo',666
By virtue of table3 referring to both table1 and table2.
This means you actually need to have 1 (one) table:
'foo','foo series','foo model', 666
And the 'problem' disappears.
Sybrand Bakker
Senior Oracle DBA

Basic doubt about Primary Key/Foreign Key in Oracle Tables

Hi,
I have a doubt whether Primary Keys/Foreign Keys are allowed in Oracle. Some of the people I know are telling me that Oracle does not encourage having Primary Keys/Foreign keys in its database tables.
However if I go to the ETRM and look for information about some of the Oracle Tables, I am informed that Primary Keys do exist. However I am being told that ETRM is not a reliable way of having correct information about table structure.
It would be great if any one of you provides me with some insight in this. Any pointers to a document would be great.
Thanks

It is not that PK/FKs are disallowed in Oracle Apps (there are some on the standard Oracle Apps tables), but they are typically not used. I am not positive what the logic behind this is, but my guess is that it was party due to the earlier versions of Oracle Apps pre-dating declarative database referential integrity in Oracle DB and also on performance issues with the standard referential integrity with the earlier versions of declarative database referential integrity.
As far as eTRM is concerned - I understood that the data is based on a design repository rather than a physical Oracle Apps DB. So all of the information in there is logically correct, but not necessarily enforced via the standard Oracle DB declarative referential integrity (rather by the application code or APIs).

How to alter or add foreign key constr to table having child rows or data

Hi,
I have a table by name DEPT in which the column DEPTNO is a primary key column and have data in it for all the columns . Now I have a EMP table where in the column DEPTNO is not having any constraint including foreign key constraint too. Now i have data in the EMP table for all the columns . now i would like to add the foreign key constraint to DEPTNO column in the EMP table referencing the DEPTNO column in the DEPT table. Both the table do not have any null values .
I need to add the foreign key without deleting the data in the EMP table.
Please advice.
Regards,
Vinesh

Hi,
I need to add the foreign key without deleting the data in the EMP table.Foreign key constraint can have only those values which are present in the primary key of the parent table or null.
When your tables are populated with values and then you are adding the constraint then,
the parent table data is only present in child table or null values.
Example
SQL> create table emp_bkp as select * from emp;
Table created.
SQL> create table dept_bkp as select * from dept;
Table created.
SQL> alter table dept_bkp
2 add constraint pk_deptno primary key(deptno);
Table altered.
SQL> select distinct deptno from emp_bkp;
    DEPTNO
        30
        20
        40
        10
SQL> select deptno from dept_bkp;
    DEPTNO
        10
        20
        30
        40
        55
SQL> alter table emp_bkp
2   add constraint fk_deptno_bkp foreign key(deptno)
3    references dept_bkp(deptno);
Table altered.
SQL> alter table emp_bkp
2 drop constraint fk_deptno_bkp;
Table altered.
SQL> insert into emp_bkp(empno,ename,deptno) values(142,'Fenny',90);
1 row created.
SQL> alter table emp_bkp
2 add constraint fk_deptno_bkp foreign key(deptno)
3   references dept_bkp(deptno);
add constraint fk_deptno_bkp foreign key(deptno)
ERROR at line 2:
ORA-02298: cannot validate (SCOTT.FK_DEPTNO_BKP) - parent keys not found
SQL> update emp_bkp
2 set deptno=null
3 where empno=142;
1 row updated.
SQL> alter table emp_bkp
2 add constraint fk_deptno_bkp foreign key(deptno)
3   references dept_bkp(deptno);
Table altered.
SQL> insert into dept_bkp (deptno,dname)values(90,'IT');
1 row created.
SQL> update emp_bkp
2 set deptno=90
3 where empno=142;
1 row updated.Twinkle

Basic doubt about Primary Keys/Foreign Keys in Oracle Tables

Hi,
I have a doubt whether Primary Keys/Foreign Keys are allowed in Oracle or not. I have been informed that Oracle does not encourage having Primary Keys/Foreign keys in its database tables. Instead it urges users to have unique constraints on the requisite columns.
However if I go to the ETRM and look for information about some of the Oracle Tables, I am informed that Primary Keys do exist. At the same time, I am being told that ETRM is not a reliable way of having correct information about table structure (at least the Primary Key information).
It would be nice if any one of you provides me with some insight in this. Any pointers to a document would be welcome.
Thanks

FYI,
There is seprate forum for Core Sql quieries
PL/SQL
Thanks

Using FOreign key constraints on tables in database.

I am student and novice in the field of ORACLE and PL/SQL and Database Creation. I had created a database consisting tables and got problem while applying foreign key constraints.
CUST_MSTR
CREATE TABLE "DBA_BANKSYS"."CUST_MSTR"("CUST_NO" VARCHAR2(10),
"FNAME" VARCHAR2(25), "MNAME" VARCHAR2(25), "LNAME" VARCHAR2(25),
"DOB_INC" DATE NOT NULL,      "OCCUP" VARCHAR2(25), "PHOTOGRAPH" VARCHAR2(25),
"SIGNATURE" VARCHAR2(25), "PANCOPY" VARCHAR2(1),      "FORM60" VARCHAR2(1));
(CUST_NO is PRIMARY KEY, )
-- EMP_MSTR
CREATE TABLE "DBA_BANKSYS"."EMP_MSTR"("EMP_NO" VARCHAR2(10),
"BRANCH_NO" VARCHAR2(10), "FNAME" VARCHAR2(25), "MNAME" VARCHAR2(25),
"LNAME" VARCHAR2(25), "DEPT" VARCHAR2(30), "DESIG" VARCHAR2(30));
(EMP_NO is primary key )
--NOMINEE_MSTR
CREATE TABLE "DBA_BANKSYS"."NOMINEE_MSTR"("NOMINEE_NO" VARCHAR2(10),
"ACCT_FD_NO" VARCHAR2(10), "NAME" VARCHAR2(75), "DOB" DATE,
RELATIONSHIP" VARCHAR2(25));
(NOMINEE_NO is primary key )
--ADDR_DTLS
CREATE TABLE "DBA_BANKSYS"."ADDR_DTLS"("ADDR_NO" NUMBER(6),
"CODE_NO" VARCHAR2(10),      "ADDR_TYPE" VARCHAR2(1), "ADDR1" VARCHAR2(50),
"ADDR2" VARCHAR2(50), "CITY" VARCHAR2(25), "STATE" VARCHAR2(25),
"PINCODE" VARCHAR2(6));
( ADDR_NO is primary key )
Problem: I want to apply foreign key constraints on ADDR_DTLS table so that Before inserting value in ADDR_DTLS table it must check, VALUE in ADDR_DTLS.CODE_NO must be PRESENT either in attribute value CUST_MSTR.CODE_NO or EMP_MSTR.CODE_NO or NOMINEE_MSTR.CODE_NO table .
I applied the foreign key constraints using this syntax
CREATE TABLE "DBA_BANKSYS"."ADDR_DTLS"("ADDR_NO" NUMBER(6),
"CODE_NO" VARCHAR2(10),      "ADDR_TYPE" VARCHAR2(1), "ADDR1" VARCHAR2(50),
"ADDR2" VARCHAR2(50), "CITY" VARCHAR2(25), "STATE" VARCHAR2(25),
"PINCODE" VARCHAR2(6),
constraints fk_add foreign key CODE_NO references CUST_MSTR. CODE_NO,
constraints fk_add1 foreign key CODE_NO references EMP_MSTR. CODE_NO,
constraints fk_add2 foreign key CODE_NO references NOMINEE_MSTR.CODE_NO);
(foreign key)
ADDR_DTLS.CODE_NO ->CUST_MSTR.CUST_NO
ADDR_DTLS.CODE_NO ->NOMINEE_MSTR.NOMINEE_NO
ADDR_DTLS.CODE_NO ->BRANCH_MSTR.BRANCH_NO
ADDR_DTLS.CODE_NO ->EMP_MSTR.EMP_NO
When I applied foreign key constraints this way, its gives a error called foreign key constraints violation. (I understand that, its searches the attribute value of ADDR_DTLS.CODE_NO in all the three tables must be present then the value will be inserted. But I want, if the value is in any of the three table then its should insert the value or its gives an error.)
Please help me out, though i put the question and i want too know how to apply the forign key in this way. and is there any other option if foreign key implementation is not pssible.

If you are on 11g you can use ON DELETE SET NULL:
CREATE TABLE addr_dtls
( addr_no          NUMBER(6) CONSTRAINT addr_pk PRIMARY KEY
, addr_cust_no     CONSTRAINT addr_cust_fk    REFERENCES cust_mstr    ON DELETE SET NULL
, addr_emp_no      CONSTRAINT addr_emp_fk     REFERENCES emp_mstr     ON DELETE SET NULL
, addr_nominee_no CONSTRAINT addr_nominee_fk REFERENCES nominee_mstr ON DELETE SET NULL
, addr_type        VARCHAR2(1)
, addr1            VARCHAR2(50)
, addr2            VARCHAR2(50)
, city             VARCHAR2(25)
, state            VARCHAR2(25)
, pincode          VARCHAR2(6) );In earlier versions you'll need to code some application logic to do something similar when a parent row is deleted, as otherwise the only options are to delete the dependent rows or raise an error.
btw table names can be up to 30 characters and don't need to end with MSTR or DTLS, so for example CUSTOMERS and ADDRESSES might be more readable than CUST_MSTR and ADDR_DTLS. Also if the Customer/Employee/Nominee PKs are generated from a sequence they should be numeric.
Edited by: William Robertson on Aug 15, 2010 6:47 PM

How to fetch column data using foreign key in adf table ?

I have created a adf table using a view that has a group id and user id column. I want to display the user name ( from user table) and group name from group table. I had created view links to the corresponding tables from the user_group view ( whose iterator is used to render the table).
It sort of works. I dragged the user name from the embedded user iterator in user_group iterator. It does find the correct user name but if I have more than one row, it displays the user name of the last row user in all rows !
Is there a solution to this problem ?

Well, I saw in the view query for the association view ( for Many-Many) that the SQL already had the joins with the two ( master) tables to the association table. So I went ahead and added the descriptive columns to the select clause. Then the selected columns showed up in the attribute list by themselves ( without my intervention). So far so good.
Then I recreated the adf table attribute by dragging these newly selected attribute to the page. I still see that the value of the attribute is the same in all the rows - this time it is the value for the FIRST row. It doesn't correspond to the foreign key for that particular row.
IS THIS A BUG ? Has anyone else ever done this ?

Missing primary foreign key in grandchild table

I have a model with a two inheritance generations.
https://www.dropbox.com/s/4rghqcmxx24bgvt/pf_logical.png
When I engineer all entities everything is fine. The child tables get their primary foreign keys:
https://www.dropbox.com/s/t4v5bexxwdrn5y1/pf_engineered.png
But when I do not engineer the child generation the grandchildren have no primary foreign keys anymore.
https://www.dropbox.com/s/ofl436sm8dua3w8/pf_missing.png
I have expected, that the grandchildren get a primary foreign key to the grandfather. But that is not the case. How can I tell the modeler to engineer such a foreign key?

Hi,
thanks for reporting the problem. I logged a bug for that.
Philip

Determine if database view column is foreign key in underlying table

Hi,
I have posted this same question to the General Database Discussions and JDBC forums.
I am using Oracle database 10g (10.1.0.4.0 - 64 bit production) standard edition on Red Hat Enterprise Linux AS release 3, JDK 1.4.2 and the latest Oracle JDBC (thin) driver.
We have a java GUI application that is a front-end for our database. Some of the data entry screens display data from database views. If a column in the view is a foreign key in the underlying table, we want to display a combo-box with the valid values so that the user can choose a correct value.
Is there some way to know whether a column in a view is a foreign key in the view's underlying table?
Thanks,
Avi.

I take that back.. I did figure something out for ya.. After reading some elses post I wrote this code... but its time to go home... I believe this will show you all the constraints and constraint types for the underlying tables of all the views for a user. You can mess with it and get it to return only FK (constraint_type = 'R') and only for a single view if ya like... The all_dependencies data dictionary view is the key to this whole operation...
select con.table_name, ucc.column_name, con.constraint_name, con.constraint_type
from all_constraints con, all_cons_columns ucc
where con.owner = user and
con.owner = ucc.owner and
con.table_name = ucc.table_name and
con.table_name in
(SELECT referenced_name
FROM all_dependencies
WHERE referenced_owner = USER
AND referenced_type = 'TABLE'
AND type = 'VIEW');

Table with n foreign key vs n tables or n foreign key vs 1 table?

Hi,
we have a scenario with n tables containing some attributes one table for one category of attribute (es: color, role, type, etc..) of a principal entity and 1 table for the principal entity with n foreign keys vs every attribute table.
Some propose to create a unique table called attributes in which put every attribute with an attributetype for each record.
My question is: the principal entity will have n foreign keys vs the same attribute table. Is this perfomant? which is the best solution?
Thanks in advance.
v.

>
we have a scenario with n tables containing some attributes one table for one category of attribute (es: color, role, type, etc..) of a principal entity and 1 table for the principal entity with n foreign keys vs every attribute table.
Some propose to create a unique table called attributes in which put every attribute with an attributetype for each record.
My question is: the principal entity will have n foreign keys vs the same attribute table. Is this perfomant? which is the best solution?
>
Ask those 'Some propose' how a foreign key to the 'same attribute table' will prevent the WRONG value from being used for a column.
1. Principal entity has a column for 'color' and a column for 'role'.
2. There are FKs on the 'color' column and the 'role' column that both point to the 'same attribute table'
3. Legal values for 'color' are: 1, 2, 3
4. Legal values for 'role' are: 10, 20, 30
What prevents someone from updating the 'color' column to a value of 20?
Ask those 'Some propose' how your one attribute table will store attributes that are of different datatypes.
1. 'color' uses numbers: 1, 2, 3
2. 'type' uses strings: 'type1', 'type2', 'type3'
3. 'holiday' uses dates: 12/25/2013, 01/01/2014
How do your 'Some propse' plan to store ALL of those values in one column? They are likely to say they will use VARCHAR2.
Ok - so how do you keep someone from updating 'holiday' to a value of 'type2' or a value of '3'?
You can't easily validate the data to begin with and you can't easily prevent 'dirty' data from getting into the system.
You also can't easily explain to ANYONE, for example new developers, how to properly use and maintain the table.
I haven't heard you mention even ONE potential benefit to doing things the way that 'Some propose'. So - DON'T DO THAT!

2 foreign keys in a table

Similar Messages

Maybe you are looking for