[READ ONLY] Subtree split of the Illuminate Database component (see laravel/framework)

Allows specifying items that are 'unfillable' via mass assignment. Handy when there are many attributes and only a couple that are not fillable. Suggested by someone on #laravel.

If you have an existing model object you can't call increment or decrement on it without setting the wheres() manually.

You can now do:

$user = User::find(1);

$user->increment('posts', 1);

Signed-off-by: Jason Lewis [email protected]

In many situations, when using Eloquent objects, we create a function to retrieve a Collection of objects based on a specific filter. Example:

public function getUsersByName ($name, $limit = 0) { return User::where('name', 'like', '%'.$name'%')->take($limit)->get(); }

In this kind of functions we want to limit the collection when some limit is specified and retrieve all objects when no limit is specified. To accomplish this we change the take function in order to consider the value 0 as to retrieve all the founded objects. Without this change we have always to implement the previous function like this:

public function getUsersByName ($name, $limit = 0) { if ($limit = 0) { return User::where('name', 'like', '%'.$name'%')->get(); } else { return User::where('name', 'like', '%'.$name'%')->take($limit)->get(); } }

When returning a Eloquent Collection, I noticed the getMutator is not applied to the resulting array and thought, it will make it better to apply getMutator method to the each result before the collection is fully converted to an array or json string.

This is a functionality to allow a query like "morphWith" but named "morphProperties" to limit the properties of morph by type.

$recommendations = Recommendation::with(['recommendable' => function (MorphTo $morphTo) {
    // This limit the properties showed for morph type
    $morphTo->morphProperties([
        User::class => ['id', 'username'],
        UserVacantion::class => ['id', 'user_id'],
    ]);

    // This eager load some relationships for morph type
    $morphTo->morphWith([
        User::class => [],
        UserVacantion::class => ['user:id,username'],
    ]);
}])->get();

As discussed here: https://github.com/laravel/framework/issues/26720 Proposal to move entity name to first place in query builder. This would fit current migration index design.

Hi Taylor,

Love your work Laravel is just awesome!!

I really care about documentation and always find my adding comments in the comments column in mysql

Till now I would do something like this

Schema::create('users', function($table) {
            $table->integer('extranet_id')->nullable()
        });

DB::update("ALTER TABLE `users` CHANGE `extranet_id` `extranet_id` INT(255)  COMMENT 'Comment about the field here!'");

This seems like double work.

So I have created a fork and added this functionality, please review and merge if all ok.

Now you can do something like this.

Schema::create('users', function($table) {
            $table->integer('extranet_id')->nullable()->comment('Comment about the field here!');
        });

I also created a test but cant seem to find where to put it. There is no tests folder or repo?

Here is the test

    public function testAddingComment()
    {
        $blueprint = new Blueprint('users');
        $blueprint->string('foo')->comment('foo');
        $statements = $blueprint->toSql($this->getGrammar());

        $this->assertEquals(1, count($statements));
        $this->assertEquals("alter table `users` add `foo` varchar(255) not null comment 'foo'", $statements[0]);
    }

Lastly I will also update the documentation when you merge the change.

Sorry I didn't update the other grammars as I not familiar with their syntax.

Fixing:  - https://github.com/illuminate/database/commit/be7246d44f4667e27a196cbf91225f758b862004#L0R906  - https://github.com/illuminate/database/commit/be7246d44f4667e27a196cbf91225f758b862004#L0R916  - https://github.com/illuminate/database/commit/be7246d44f4667e27a196cbf91225f758b862004#L0R919

Bigint has too big a range to be returned as an int in PHP. It is returned as a string, which can be confusing when expecting an int to be returned. In addition, the range of integer is suitable for most cases: -2147483648 to +2147483647.

This rather large pull request implements a contains() method for the collection class.

That method checks whether an element with the given primary key (ID) is part of the collection. To make this simpler, I made sure that every item in the collection is indexed by the ID. That makes up the largest part of this pull request (along with modifying the unit tests appropriately).

Example

What does that allow us to do?

For example, if you have a user with a bunch of associated rules, it allows you to easily check whether your user is associated with the rule with ID 5 like this:

if ($user->roles->contains(1))
{
    // do something...
}

Notes & questions for Taylor

I am, let's say, 90-percent sure that this implementation is fine (tested, after all). I doubt there is a central place where this could be done, except for the collection constructor maybe, but I didn't want to add any ugly instanceof-like code (meta programming etc.). I usually found a place to set the keys in a place where the arrays were being assembled anyway, because I tried to avoid having to iterate over all the elements just for this purpose.

Also, about testing: the feature is basically implicitly tested in the existing tests now because they rely on certain IDs being returned as keys, but I wonder whether I should add methods testing explicitly this...

isGuardable() returns false for columns that are not guardable. So the "!" sign should be removed from the return statement of isGuarded() function before isGuardable(). Otherwise normal attributes which are to be Posted to the database gets guarded and causes problems.