Call to undefined method Illuminate\Database\Query\Builder::lists() when seeding after updating to Laravel 5.3

Title: Understanding Call to undefined method issue when seeding after updating to Laravel 5.3 Body: Updating to Laravel 5.3 can sometimes bring unexpected issues, such as the "Call to undefined method" error in your application. In this blog post, we will take a look at a common case where you get an error message when seeding after updating to Laravel 5.3 and some possible solutions to fix it. The issue occurs due to a change in Laravel's default behavior from earlier versions. Before Laravel 5.3, the 'lists()' method was available for the Database Query Builder. However, with the update, this method has been removed as it was considered deprecated and replaced by other methods that provide more functionality. The original problem code sample looks like this:

        User::create([
        'name' => 'No User',
        'email' => 'nouser@nouser.com',
        'password' => bcrypt('0'),
        'provider' => '0',
    ]);

Here, you are using the 'lists()' method within your User model:

        $users = User::lists('name');

In Laravel 5.3, this line would cause an exception because there is no more 'lists()' method in Illuminate\Database\Query\Builder class. To fix it, you could replace the usage of 'lists()' with an alternative method, such as 'get()', which returns a collection object instead of a comma-separated list:

        $users = User::get();

In this case, we will use the 'pluck()' method that was introduced in Laravel 5.3 to return only the specified column as an array. So your code would look like this:

        $userNames = User::select('name')->pluck('name');

In another file where the issue occurs with a similar problem (using 'lists()' method in Tournament model):

        Tournament::create([
        'user_id' => 1,
        'name' => "name",
        'dateIni' =>  $dateIni,
        'dateFin' =>  $dateIni,
    ]);

The fix is similar, you should replace the usage of 'lists()' with an alternative method. For example, using 'get()' in this case:

        Tournament::create([
        'user_id' => 1,
        'name' => "name",
        'dateIni' =>  $dateIni,
        'dateFin' =>  $dateIni,
    ]);

Alternatively, you can change the code to use built-in methods like 'groupBy()' or other customized functions that will fit your application. With the help of these alternative methods, you should be able to resolve the issue and have a smooth transition to Laravel 5.3. In conclusion, understanding the changes in database functionality between Laravel versions can save you from unexpected problems like this one. Replacing 'lists()' with more efficient methods such as 'get()', 'pluck()', or custom functions will ensure your application runs smoothly after updating to newer versions of Laravel framework.