@saullo Well, when it comes to Relational Databases and Relational Database Theory, in order to consider a Database Schema Relational it must satisfy some very strict Rules (search for Codd's Rules about RDT on google for more) and one of those rules is that EACH field (cross of column and row) must contain ONLY 1 VALUE.

If you were to reverse it and do what you said, since an employer CAN HAVE MANY JOB LISTINGS that column "job_id" should contain multiple values...just because (1) Employer can list (MANY) jobs. I hope you understand.

Practically you can do it. You can actually do whatever you want. But it will stop you from scaling up any app in the long run. I once did it with IDs just because I didn't want to make another table so a column had values such as : "5|1|41|919|231|" IDs separated by "|" . Trust me...it's bad...it's really bad when you want to scale your application even just a little bit.

So to conclude, the answer is NO. Just don't. Especially now that you're a beginner stay inside "good practices" just to learn these first and maybe later you can consider of breaking the rules.

Peace and happy coding brother!

Two Key Eloquent Relationship Types

Updated Series Available