Create new on other than default connection

[reno1979]

• Laravel Version: beta (used this proposed fix: [5.4] Use parent connection if related model doesn't specify one #16103 scheduled for laravel 5.4)
• PHP Version: 7.0.1
• Database Driver & Version: Mysql 5.6

The model create method keeps using the default db.
We are using artisan tinker, and tried the following:

\App\FeatureGroup::on('otherConnection')->getModel()->create(['name'=>'test']);
// a new row is inserted in the default db, but should be in the otherConnection db
// firstOrCreate does the same :( 

/* OUR WORKAROUND */

$featureGroupModel = new \App\FeatureGroup;
$featureGroupModel->setConnection('otherConnection');
$featureGroupModel->save();

$featureGroupModel->id; // the given id is from the new table row in otherConnection db :)

// or 

\App\FeatureGroup::on('otherConnection')->getModel()->firstOrNew(['name'=>'test'])->save();

[GrahamCampbell]

Please upgrade to the latest php 7.0.x or 7.1.x.

[themsaid]

@reno1979 that fix wasn't related to creating model, just querying related models on the parent connection.

I've submitted a proposal to add a connection argument to the create method, not sure if it'll pass though since you can already do it by constructing the instance yourself.

#17392

[reno1979]

@themsaid Thank you for looking in to this. Constructing a new instance is our current work arround. It just seems odd that the create methods always falls back to the default connection settings.

Using the workaround (instance with correct connection settings) causes a lot of additional code...
It would be more intuitive to just use ::

\App\FeatureGroup::on('otherConnection')->getModel()->create(['name'=>'test']);