How to properly restructure the database for Laravel in order to correctly use the features of Eloquent?

Question

Laravel

Thanks to D''s advice and a correct kick, we managed to solve the previous hasMany problem.
But it turned out that the existing tables are not adapted for Laravel ... and they need to be somehow reformatted in order to link them. I would be grateful for practical advice-help...
What I have:
1) Reference table - countries (names of countries)
Structure:
id | country_name
2) User registration table - users
Structure
id| name | country_id
3) Table with holidays in countries - holidays
Structure
id | country_name (text) | date
I thought that I would link users and holidays, but that wasn't the case... in the holidays table, the id-list is just the serial number of the record, and the country name is stored in text...
Task 1: make the table structure holidays
id (holiday) | country_id | date
If I understand correctly, then I do a normal join to substitute the name of the country by its country_id.
I will receive approximately the following array of objects
id (holiday) | country_id | country_name (from countries) | date
In fact, while writing a question-request (an hour ago) I understood how to solve .... and it's a pity to delete ...
that's what I got ....

public function index(Holiday $holiday)
    {
    $holidays = $holiday -> getHolidays();

    return view('bday.index', ['holidays' => $holidays]);
    }

In the Holiday model:

class Holiday extends Model
{
  protected $table="holidays";
       
       public function getHolidays() {

  return $this->select(DB::raw("id,day,holiday,country_id,country_rus2,DATEDIFF(
             CONCAT(
                 YEAR(CURDATE()),
                 '-', MONTH(day),
                 '-', DAY(day)
                 ),
         CURDATE()
         ) AS daysto"))
    ->havingRaw('daysto BETWEEN 0 AND 10')
    ->get();

  }

  public function name() {
      return $this->hasOne('App\Country','rus_name','country_rus2');
  }

  public function users() {
      return $this->hasMany('App\User','country_id','country_id');
  }
}

Well, in fact, for now, an empty, initialized Country model with binding to the countries table,
well, something like this ... again a garden? ...
again, I repeat the task solves .. really too many requests ...
I'm ready for you to criticize, but if so, how should it be?)

Answer 1

If I were you, I would add a country_id foreign key to the holidays table

$table->integer('country_id')->unsigned()->index();
$table->foreign('country_id')->references('id')->on('countries')->onDelete('cascade');

And in the same migration, I would write a script that looks for country IDs by country_name and fills in this new column. In this case, there is less hemorrhoids in the future and the code is cleaner.