Seems to struggle with relationships where the source and target column have the same name about laravel

[finiteinfinity]

Hi @WeaponX86,

Try setting 'relation_name_strategy' => 'foreign_key' in the models.php config file please?

I'm not 100% this will solve your issue, but setting that config value should use the foreign key name (where possible) to generate the relation names instead - which I'm hoping solves your naming issues.

[WeaponX86]

I should mention I'm running:

• PHP v7.3.3
• Laravel Zero v8.10.0
• reliese/laravel v1.1.6

I have "relation_name_strategy" set to "foreign_key" already. The only other thing I changed in the config was setting the namespace:
'namespace' => 'App\Models\Shard',

My database contains 346 tables with 501 total foreign keys. All keys are named like {TABLE}_ibfk_{INT}. All of the generated models just get dumped with the column name for the method which is unusable because it conflicts with the actual column name attribute.

I generated the models like this:
php artisan code:models --schema=my_schema

Example code:

		$org = User::firstWhere('user_id', 254)
		->with('org_id')
		->get();
		//Log::debug($org); // Array with one object

		Log::debug('Organization name: '.$org[0]->org_id->org_name); 

Throws this error:

Here's another example of a table definition and the resulting model: