ftiersch

I think the "findOrFail" is unneccessary since you seem to implicitly bind the route to a configurator object by typehinting it.

Try changing your controller to this:

public function show(Configurator $configurator)
    {
        return view('configurator.show', compact('configurator'));
    }

Gotta agree with @bobbybouwmann here. "Magical" usually means "annoying the next person working on it because he has to find out what the f is going on".

Your solution with the directive sounded great to me. Expressive and explicit and no unwanted complications.

You're right, that worked. I thought it should work inside a renderless component too for reusability but that fixed it. Thanks!

That depends a lot on the kind of thing you want to create. What I mean is that you shouldn't think too much in rigid structures.

The 1:n or m:n only describes the number of possible entities on each side. If they make sense without another totally depends on your application.

So a 1:n relationship is usually where one of your entities has the ID of the other one in it's database table. That's what creates the relationship between the two. So with the car / color example the "cars" table would have a "color_id" column.

Now when you make that "color_id" column NULLABLE there can be a car without a color. Think of a factory that creates cars but they only get painted at the end. So basically until the car is at the end it doesn't have a color and the "color_id" column would be NULL.

Can't really think of a real world example right now, sorry :D

In your blade:

@forelse($posts as $post)
    {{ $post->title }}
@empty
    No results found
@endforelse

Like I said - I'm not sure about your setup. Like what the $type variable does and why you need that and where the hasManyThrough relationship is :) If you can give a little more context I'm sure there are some improvements possible.

Whoops. I just tried and you're right. :) Didn't even know that, I always used LIKE for case insensitivity.

Sorry @mstrauss , totally got that wrong.

Hey,

I'm currently trying to use a custom directive (from https://github.com/simplesmiler/vue-clickaway) in a scoped slot but I get "Failed to resolve directive". Is there any workaround around this?

// this is the MainNav component

import { mixin as clickaway } from 'vue-clickaway';

    export default {
        mixins: [clickaway],
        data() {
            return {
                isOpen : false,
            }
        },
        methods: {
            hide() {
                this.isOpen = false;
            }
        },
        render() {
            return this.$scopedSlots.default({
                isOpen      : this.isOpen,
                hide : this.hide,
            });
        },
    }

// and here I'm using it

<main-nav>
        <div slot-scope="slotScope">
            <nav class="mainnav" v-on-clickaway="slotScope.hide">
            </nav>
        </div>
    </main-nav>

It is not returning the information, it is only printing the information. But your variable will just be "true". When you pass "true" to the function you get the information from the function but it will not print it.

value='input'

should be case sensitive - meaning it is sensitive to casing and "input" is something else than "iNput" because the case is different.

value LIKE 'input'

This would be case insensitive

I would run the sanity checks with a validator.

So in a controller you could do this:

$this->validate(request(), [
    'datevalue' => 'required|date',
]);

Haha... god damnit... you're onto me! Should be a correct date of course :)

Otherwise:

Carbon::createFromFormat('d-m-Y', '31-12-2019')->toDateString();

I'm a little confused about your setup :)

But if you have a hasManyThrough relationship you can change it to hasOneThrough which basically gives you the object right away so you don't have to call first() on it.

Do you mean case insensitive? Because the default way should be case sensitive.

I like to use Carbon for that but you can also use strtotime from PHP itself.

(new Carbon('32-12-2019'))->format('Y-m-d');

// or

(new Carbon('32-12-2019'))->toDateString();

Almost.

Yes, m:n (usually) means m can exist without n but they have a relationship with each other - in that case one entity of n can have multiple relationships with multiple entities of m and the other way around too.

Example: One Product in an online store can be bought by multiple customers. But of course every customer can also buy multiple products.

For your second one:

Depends on the relationship. There can still be an entity one without the entity two but a lot of times it's the way you said, that one entity only makes sense with the other one.

So for example lets say you have a table "colors" and a table "cars". A car without a color doesn't make sense. A color without a car makes sense. So if every car can have only one color here would be a 1:m relationship. If every car could have multiple colors it would be m:n.

Brand::find([$ids])->each(function ($brand) {
    $brand->toys()->create();
});

You have to work through the collection because a collection is not a "Brand" model so it doesn't know the toys() relationship :)

You could simply do this (if I understand your code correctly):

IndividualProfile::first();

Read the documentation you've posted and you will know ;-)

You give it "false" as a return parameter so it will return "true" after printing your information (instead of returning it). And when you echo "true" you get 1 because it's the same thing.

Probably you need a recursive blade partial that you can include. So you can do this:

// this would be the partials/category.blade.php

@foreach ($categories as $category)
    <div>
        <p>{{ $category->name }}</p>

        @include('partials.category', ['categories' => $category->child_categories])
    </div>
@endforeach

// in your Category model
public function child_categories() {
    return $this->hasMany(self::class, 'parentId');
}

And depending on your number of nested levels you could also eager load some levels to avoid looooaaads of queries to get all the layers:

$categories = Category::with(['child_categories.child_categories.child_categories.child_categories'])->get();

https://laravel.com/docs/5.8/validation#rule-unique

There is an option to ignore a certain row for this rule :)

My example creates a new Profile object every time a user is created. But that probably won't work that easy because your Profile has a lot of columns that need values. So either you make all those columns nullable() or you have to create the profile "manually" when you create a user during registration and fill it with the necessary values :)

Your select has the name "name", not "u_id"...

That is exactly what middlewares are for ;-)

Add a middleware that has exactly the "if role = employee -> redirect" code in it and it shouldn't bring any issues for every user. And the added benefit is you don't have to execute all your code before checking that inside a blade file at the end (where it shouldn't sit anyway because templates are for presentation, not for logic).

You can use Eloquent events or Observers for this.

In your User model for example:

public static function boot() {
    parent::boot();

    self::created(function ($model) {
        $profile = new Profile();
        $model->profile()->save($profile);
    });
}

Sure you can but you should definitely rework your variable names ;-)

$toy = Toy::create($request);
$toy->brands()->attach($brand_id);

Try this

Looks like there is an invisible symbol before your APP_NAME

If it is a request object:

'data' => $request->only('repair_report_einkaufen', 'repair_report_einkaufen1'),

Are your relationships (so the methods) called "toys()" and "brands()"? And does the brands() relationship work if you use it normally on a Toy model?

If you add a new childs toy yes, that's all you need. But the toy needs to have all its brands already in the toy_brand relationship.

Aah okay. That makes more sense. But why can a toy have many brands? Isn't a toy usually by a single brand?

Anyway. In that case you would have to add the relation between toy and brand and between toy and child. The rest should work as expected then.

Wait, I think you have an error in your database planning there.

One child can have multiple toys, right? But one toy can only be owned by a single child right? Also one toy is of a single Model but every Model can have multiple toys?

You don't have to, it works with your existing model_toy relationship. with() also gets the values dynamically.

You have a field "c_id" in your table that you are not filling... It's right there in the error message.

Yeah, that would work. You just put the name of the relationships in the with.

With a subquery. Something like this:

SELECT * FROM child_toy WHERE EXISTS (SELECT * FROM model_toy WHERE model_id = ?)

Not sure about the exact syntax but something like that :)

No, that query actually uses 2 subqueries (which could make it slow with a lot of data).

So basically it says "Check if this Child has a Toy that has at least one Model with the ID of the given model"

The link doesn't help a lot if it's on your localhost ;-)

Add this at the top of your file after the namespace:

use Illuminate\Http\Request;

You could do this on your Child model:

function hasToyWithModel($model) {
    return $this->toys()->whereHas('models', function ($query) use ($model) {
        $query->where('id', $model->id);
    })->exists();
}

I think that should work but I'm not sure if that's the most performant way.

Do you have a pivot table with all three foreign keys in it or do you have multiple pivot tables?

What does it say if you do

dd($data); 

after you got your data from the request?

You cannot extend from multiple classes. Authenticatable already extends Model so you don't need to extend from it yourself.

Of course it has... But things like Carbon and Collections just put an easier to use API wrapper around ootb things :)

Maybe createFromFormat works better:

Carbon::createFromFormat('d/m/Y', $request->get('begin'))

$date = '10/03/2019';

Carbon::parse($date)->toDatetimeString();

You get a normal php array back. So with @tykus method you get all the names as a new array. Or you go through them with foreach()

You mean you send it TO your view? Can you show more code?

http://image.intervention.io/api/exif

Have you seen the part about php being combiled with --enable-exif?

Are all the keys unique?

array[test] = 10;
array[test] = 20;

This would only arrive as array[test] = 20 because the second value overwrites the first one.