You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, although we explicitly check to see if the id column exists, we do no validations on IDs that link to other tables.
For example, if you're trying to import games owned by people, and you fill the attendee_id column with IDs, any ID that doesn't exist in the DB will cause the unhelpful "Import unsuccessful" error because it fails at the session.commit() step. Ideally, what would instead happen is that it imports all the rows with working attendee_id columns, and prints a list of the failed rows.
Right now, although we explicitly check to see if the
idcolumn exists, we do no validations on IDs that link to other tables.For example, if you're trying to import games owned by people, and you fill the attendee_id column with IDs, any ID that doesn't exist in the DB will cause the unhelpful "Import unsuccessful" error because it fails at the session.commit() step. Ideally, what would instead happen is that it imports all the rows with working attendee_id columns, and prints a list of the failed rows.