JORGE MALDONADO wrote
> If a table has a foreign key on 2 fields, should I also create an index
> composed of such fields?
Yes.
If you want to truly/actually model a foreign key the system will require
you to create a unique constraint/index on the "primary/one" side of the
relationship.
CREATE
I really appreciate your fast and very complete answer.
If a table has a foreign key on 2 fields, should I also create an index
composed of such fields?
For example:
---
Table Sources
---
1. src_id
2. src_date
3. Other fields . . .
Here, the "primary key"
JORGE MALDONADO wrote
> I have a table with fields that I guess would be a good idea to set as
> indexes because users may query it to get results ordered by different
> criteria. For example:
>
> --
> Artists Table
> --
> 1. art_id
> 2. art_name
> 3. art_bday
> 4.
I have a table with fields that I guess would be a good idea to set as
indexes because users may query it to get results ordered by different
criteria. For example:
--
Artists Table
--
1. art_id
2. art_name
3. art_bday
4. art_sex
5. art_country (foreign key, there i
