Thank you guys for your answers, ron - it was just an example Luther - this table was migrated from our old data and we do intent to use auth instead
still, it's good practice to always have unique field or combination of fields in a table besides the id, id is for machines, not suitable for the real world.... my understanding is that IS_NOT_IN_DB is not forced at the database level like the "unique" keyword, I'm looking for something like the unique keyword only for multiple fields, not just one is there something like this?
