Saving with relations (hasOne, hasMany)

@cristian9509 The other way around. You need dealership saved first, then you can assign business.

In other words:

// save user and business
// do what you need with the dealership, then..
$dealership->save();

$dealership->businesses()->save($business);

You may want to do this, to save one query:

// user stuff
$user->save();

// dealer stuff
$dealership->save();

// business stuff
$business->user()->associate($user);
$business->dealership()->associate($dealership);
$business->save();

This is just a quick look but I think you'll have to do $dealership->save();

Then $buissness->dealership()->attach($dealership->Id);

@JarekTkaczyk First option is not working because I am using user_id on the business table rather than an id. However the second option worked nice. Why would first option not work?

Cause you can not call the save method on related model/object. You need to call attach as @Goldenstat mentioned.

@cristian9509 Both work. If you have problem, then show the code and error - don't work says nothing ;)

@bugsysha 1 you can call save on any model, 2 it is calling save on HasMany relation, 3 attach will throw exception - it's on BelongsToMany relation, not on HasMany.

@JarekTkaczyk Here is the code:

$user = $request->user();

        $business = new Business();
        $business->name = 'JohnDoe Inc.'
        $business->save();


        $dealership = new Dealership();
        $dealership->name = 'Ford/Lincoln Dealer';
        $dealership->save()

        $dealership->businesses()->save($business);

And the error:

QueryException in Connection.php line 636: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'id' in 'where clause' (SQL: update `businesses` set `dealership_id` = 1, `updated_at` = 2015-09-16 22:15:55 where `id` = 0)

First of all the id in the where clause should be user_id. Secondly, the business does not have an id column because as I said I use the user_id. Thirdly, businesses user_id is not autoincrementing. So the businesses table must have a user connected to it to exist.

@cristian9509 You're saving $broker- what's that?

And You just answered your own question - you need to set PK of the model to user_id, otherwise it will try to update using default id column.

@JarekTkaczyk my Business model does not have a PK. I tried setting it on the migration and was getting an error. I'll try again maybe I was doing something wrong. The $broker was a bad copy paste with another variable. I corrected the code.

@cristian9509 It doesn't matter whether it's auto incrementing or not here. You're getting error because you didn't set protected $primaryKey = 'user_id' in that model, so eloquent tries to update using id.

@JarekTkaczyk Now it makes sense. But can I set that primary key in the model and still not have it set in the migration?

You still need to create the incremental key in your migration and add it to your model

@JarekTkaczyk Last time I used it it did not work. Will try it again when it comes up. Hope you are right cause that would be so much easier.

@JarekTkaczyk Both options work fine! I added the protected $primary = 'user_id'; , changed my migration to have 'user_id' as primary key and now I can do both options. However I feel that the second option is much clearer. It's easier for when I read my code later on. Thank you.