Final answer:
To list all FDs and eliminate partial FDs, you should understand Functional Dependencies in database theory, identify non-prime attributes functionally dependent on part of a candidate key, and adjust the schema to ensure only full functional dependencies remain, aligning with 3NF or BCNF standards.
Step-by-step explanation:
When you are asked to list all FDs (Functional Dependencies) in a database and to eliminate partial FDs, you are dealing with a database normalization task. Functional Dependencies are a core aspect of database theory, which help understand the relationships between attributes in a relation. A partial FD occurs when a non-prime attribute is functionally dependent on a part of a candidate key, rather than the whole key.
To identify and eliminate partial FDs, one would typically decompose the relation into smaller, well-structured relations that would store the data without redundancy and potential update anomalies. This is often part of the process to normalize a database to the Third Normal Form (3NF) or Boyce-Codd Normal Form (BCNF). In each step, you ensure that every non-prime attribute is fully functionally dependent on a candidate key of the relation, thus eliminating partial dependencies.
With this in mind, you would proceed by first listing all the functional dependencies in the given relation. Then, separate them into full functional dependencies and partial ones. Finally, you would adjust the schema to ensure that only full functional dependencies are left, which may involve creating new relations or altering the candidate keys.