CSV problem with STAFF tables

brigmcneil · 10-12-2025, 05:50 PM

Hopefully this can be fixed in FHM12...
I am playing with the CSV exports and I am noticing that the STAFF_MASTER has duplicate STAFFID's. It appears that the duplicates are eliminated if you ignore RETIRED = 1 rows. But, there is also a problem where there are also duplicates in the STAFF_RATINGS table and there is no distinguishing characteristic indicating which one belongs to the ACTIVE staffer.

brigmcneil · 10-26-2025, 06:01 PM

This one is still an issue and really renders the STAFF_RATINGS csv useless, as you cannot link STAFF_MASTER to STAFF_RATINGS. Look at Geoff Ward and Bob Gainey as examples. In my save, they both get STAFFID = 176. Gainey is retired, but the STAFF_RATINGS has 2 rows of 176, so you cannot distinguish which is which.

JeffR · 10-27-2025, 07:12 AM

We'll have a look. If this is a situation where re-using the staff ID's is causing the problem, it may be unavoidable, but in that case we should add the retired flag to STAFF_RATINGS so that can be filtered as well.

brigmcneil · 10-27-2025, 01:15 PM

I think the latter would work - it basically makes ID + retired status = primary key

10-12-2025, 05:50 PM	#1
brigmcneil Minors (Triple A) Join Date: Feb 2016 Posts: 229	CSV problem with STAFF tables Hopefully this can be fixed in FHM12... I am playing with the CSV exports and I am noticing that the STAFF_MASTER has duplicate STAFFID's. It appears that the duplicates are eliminated if you ignore RETIRED = 1 rows. But, there is also a problem where there are also duplicates in the STAFF_RATINGS table and there is no distinguishing characteristic indicating which one belongs to the ACTIVE staffer.

10-26-2025, 06:01 PM	#2
brigmcneil Minors (Triple A) Join Date: Feb 2016 Posts: 229	This one is still an issue and really renders the STAFF_RATINGS csv useless, as you cannot link STAFF_MASTER to STAFF_RATINGS. Look at Geoff Ward and Bob Gainey as examples. In my save, they both get STAFFID = 176. Gainey is retired, but the STAFF_RATINGS has 2 rows of 176, so you cannot distinguish which is which.

10-27-2025, 07:12 AM	#3
JeffR FHM Producer Join Date: Apr 2002 Location: Kelowna, BC Posts: 17,432	We'll have a look. If this is a situation where re-using the staff ID's is causing the problem, it may be unavoidable, but in that case we should add the retired flag to STAFF_RATINGS so that can be filtered as well.

10-27-2025, 01:15 PM	#4
brigmcneil Minors (Triple A) Join Date: Feb 2016 Posts: 229	I think the latter would work - it basically makes ID + retired status = primary key