I think that development errors on legacy RDBMS schemes like UML on MS Excel are worth consideration – for example, employing Laravel. Take a lookt at php artisan db:seed CarStatusSeeder:


  Call to undefined method Illuminate\Database\Eloquent\Relations\HasOne::getOwnerKeyName()

  at vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php:50
     46▕      * @throws \BadMethodCallException
     47▕      */
     48▕     protected static function throwBadMethodCallException($method)
     49▕     {
  ➜  50▕         throw new BadMethodCallException(sprintf(
     51▕             'Call to undefined method %s::%s()', static::class, $method
     52▕         ));
     53▕     }
     54▕ }

  • Bad Method Call: Did you mean Illuminate\Database\Eloquent\Relations\HasOne::getForeignKeyName() ? 

      [2m+4 vendor frames [22m
  5   [internal]:0

      [2m+11 vendor frames [22m
  17  [internal]:0

Doesn’t sound promising, as the code is lean and clearly looking – CarStatusSeeder.php:

     * Run the database seeds.
     * @return void
    public function run()
        $car = Car::factory()->create();

So, the documentation hints the same, and there is no problem – virtually. Let’s take a shift to a Slim 4 PSR based development.

Enterprise stakeholders

%d bloggers like this: