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
If foreign key constraint for user_id is added in access_tokens table, shall it be an additional overhead when there are large number of users. I am asking this because, when I add foreign key constraint to user_id field, the index on it is removed, and indexing is for sure, good when there are large number of users. Or is it that adding a foreign key constraint to a column is automatically indexed.
So what to use, foreign key constraint or index for user_id?
The text was updated successfully, but these errors were encountered:
SamarRizvi
changed the title
Question: Shall adding foreign key constraint in 'access_tokens' table be an additional overhead
Question: Shall adding foreign key constraint in access_tokens for user_id column table be an additional overhead
Jun 9, 2017
SamarRizvi
changed the title
Question: Shall adding foreign key constraint in access_tokens for user_id column table be an additional overhead
Question: Shall adding foreign key constraint in access_tokens table for user_id column be an additional overhead
Jun 9, 2017
If foreign key constraint for
user_id
is added inaccess_tokens
table, shall it be an additional overhead when there are large number of users. I am asking this because, when I add foreign key constraint to user_id field, the index on it is removed, and indexing is for sure, good when there are large number of users. Or is it that adding a foreign key constraint to a column is automatically indexed.So what to use, foreign key constraint or index for
user_id
?The text was updated successfully, but these errors were encountered: