skyrun
Active Member
i'm 90% sure that there is an issue with the new join code where it's not using the correct columns with the correct table when you build the join. when both are the same name, this doesn't show as being an issue... but when the columns in the join are named something else like 'element_id', then an SQL error is created with it looking for a column named 'from column' in the 'to' database... so looking for sf_score_element.id in the example below. works fine if both columns are named the same things, but doesn't work so well when they're not...
so if i change the from column to 'element_id' (which is what it should be in the activity score list), then i get a SQL error looking for sf_score_element.element_id which doesn't exist since element_id is in the 'from' table, not the 'to' table.
so if i change the from column to 'element_id' (which is what it should be in the activity score list), then i get a SQL error looking for sf_score_element.element_id which doesn't exist since element_id is in the 'from' table, not the 'to' table.