Background:
I have been working on a sport card database for a long time in MS Access but am at a point where I needed to enlist help from a former colleague who specializes in Oracle, SAP, PostgresSQL.
Summary:
In MS Access I had so many M2M relationships that were handled through I believe what are called bridge or junction tables. My colleague has me re-designing the database in excel just to map the tables initially and I notice i am constructing what appears to be lookup fields and multivalued fields at his direction.
Question:
Lookup fields and multivalued fields are said to be a very bad practice in MS Access. Does the same hold true for other DBs like mysql or postgres?
Thanks in advance for your help!
I have been working on a sport card database for a long time in MS Access but am at a point where I needed to enlist help from a former colleague who specializes in Oracle, SAP, PostgresSQL.
Summary:
In MS Access I had so many M2M relationships that were handled through I believe what are called bridge or junction tables. My colleague has me re-designing the database in excel just to map the tables initially and I notice i am constructing what appears to be lookup fields and multivalued fields at his direction.
Question:
Lookup fields and multivalued fields are said to be a very bad practice in MS Access. Does the same hold true for other DBs like mysql or postgres?
Thanks in advance for your help!