Tray2

I've done this to validate on two fields

[
            'first_name' => 'required|unique:authors,first_name,' . null . ',id,last_name,'. $request->last_name,
            'last_name' => 'required'
 ]

I would probably use forks for each project and just version control the files specific to each project.

Seeding can be used both for testing and for seeding the production data.

Check database seeders here

https://laravel.com/docs/5.8/seeding#introduction

Try

php artisan cache:clear

Run this command and try again

php artisan view:clear

I would not create a table for each state's cities but rather use a foreign key to connect them.

Something like

mysql> desc states;
+----------------+------------------+------+-----+---------+----------------+
| Field          | Type             | Null | Key | Default | Extra          |
+----------------+------------------+------+-----+---------+----------------+
| id             | int(10) unsigned | NO   | PRI | NULL    | auto_increment |
| name           | varchar(255)     | NO   |     | NULL    |                |
| short_name          | varchar(10)     | NO   | UNI | NULL    |                |
| created_at     | timestamp        | YES  |     | NULL    |                |
| updated_at     | timestamp        | YES  |     | NULL    |                |
+----------------+------------------+------+-----+---------+----------------+ 

mysql> desc cities;
+----------------+------------------+------+-----+---------+----------------+
| Field          | Type             | Null | Key | Default | Extra          |
+----------------+------------------+------+-----+---------+----------------+
| id             | int(10) unsigned | NO   | PRI | NULL    | auto_increment |
| name           | varchar(255)     | NO   |     | NULL    |                |
| state_id          | int(10)unsigned     | NO   | UNI | NULL    |                |
| password       | varchar(255)     | NO   |     | NULL    |                |
| created_at     | timestamp        | YES  |     | NULL    |                |
| updated_at     | timestamp        | YES  |     | NULL    |                |
+----------------+------------------+------+-----+---------+----------------+

Or you could use the state's acronym together with the name to create the primary key.

Do a descon both tables and compare them.

mysql> desc users;
+----------------+------------------+------+-----+---------+----------------+
| Field          | Type             | Null | Key | Default | Extra          |
+----------------+------------------+------+-----+---------+----------------+
| id             | int(10) unsigned | NO   | PRI | NULL    | auto_increment |
| name           | varchar(255)     | NO   |     | NULL    |                |
| email          | varchar(255)     | NO   | UNI | NULL    |                |
| password       | varchar(255)     | NO   |     | NULL    |                |
| remember_token | varchar(100)     | YES  |     | NULL    |                |
| created_at     | timestamp        | YES  |     | NULL    |                |
| updated_at     | timestamp        | YES  |     | NULL    |                |
+----------------+------------------+------+-----+---------+----------------+

This is my users table.

Yes you do since you call it $shares in your controller instead of $share.

Eaither change in the controller or the view. I'd go for the controller option.

The id of the users table must be the same type as the one in your foreign key.

Try removing the @foreach since it's only one share found you don't need to loop over it.

So if created_at equals updated_at then it's a new project and if updated_at greater then created_atit's published?

I suggest you add a published_at field to your table and use it to determine if it's published or not.

How long is a project new? five days?

You can use carbon for that comparsion

https://carbon.nesbot.com/docs/

The package @Ty suggested is not recommended since it clutters up your views and makes them harder to debug.

It's very easy but quite tedious to create lots of forms but it's still the best way to do it.

Call me old school but I prefer the old way of doing joins and keeping my Eloquent simple so I'd hide the implementation in a database view so I can do this instead.

$records = RecordsView::where('field', $value);

Something like

<tr>
@foreach($collection->keys() as $key)

    <th>{{ $key }} </th>

@endforeach
</tr>
<tr>
@foreach($collection as $record)
   @foreach($collection->keys() as $key)
    <th>{{ $collection[$key]</th>
    @endforeach
@endforeach
</tr>

might work

Then it's better to use

CREATE OR REPLACE VIEW

Then it will always recreate it.

You can alway use custom messages. Something like

protected $messages = ['field.required' => 'This bad boy must be unique'];

public function store(Request $request)
{
   $request->validate(['field' => 'required], $this->messages);
   
   //Do the storing here
}

Check that you have the correct classes in your use statments since this is most likely the issue..

That usally means that it can't find your factory class.

Check your use statements and make sure that they are correct.

Check this link it might be what you are looking for

https://laravel.com/docs/5.8/broadcasting#introduction

I have a bad feeling in my stomach when reading your code. When you start using numbers in your field names you have a bad design. I suggest using another table for all those fields that way it's scalable out of the box.

Classic one to many scenario.

Yes, don't use the form builder. It's not needed and it creates code that is harder to read and debug.

Try removing IF EXISTS. It might solve your issue. If the syntax is wrong it should squawk.

What database are you using?

No, it will not work properly since you can't commit each session by itself in MySQL. In the Oracle database you can you autonomous transactions where each statement can be commited without commiting everything in the session.

While it would work to write it that way you wouldn't benifit from it.

MariaDB is a fork of MySQL created by some of the MySQL developers who didn't like the way MySQL was going.

Use the slug helper instead

https://laravel.com/docs/5.8/helpers#method-str-slug

It has to do with the hashing algorithm in MySQL 8. You can configure it to use the legacy hashing. That way you can use version 8. However I suggest you uninstall MySQL and install MariaDB instead.

https://community.jaspersoft.com/wiki/uninstall-mysql-mac-os-x

https://www.javatpoint.com/how-to-install-mariadb-on-mac

There are some issues with MySQL 8 and PHP. They have changed stuff in the connection in MySQL 8. There might have been a fix in later versions of PHP so try upgrading it. Or use MariaDB or an earlier 5.7 version of MySQL.

Hm,

Looks a bit like it's more code to add then just

public function post()
{
   return $this->belongsTo(User::class);
}

But then again I just took a fast peek at the docs.

You can refactor out the validate to the Model class and just pass the rules.

protected function validate(Request $request, $rules)
{
    return $request->validate($rules);
} 

And in your controller

protected $rules = ['email' => 'required|email'];

public function update(Request $request)
{
     $this->validate($request, $this->rules);

     $user = User::find(Auth::user()->id);
     $user->email = $request->email;
     $user->update();

     return response()->json([]);
} 

Or similar.

Aah I didn't read that it was postgres and I'm not familiar with that dialect of SQL.

I suggest you buy Matt Stauffer's Laravel Up And Running 2nd Edition. There you will get some more context to the topics. It's a great companion to Laracasts.

https://www.amazon.com/Laravel-Running-Framework-Building-Modern/dp/1492041211/ref=sr_1_fkmrnull_1?crid=3Q8DYPKTWMXIX&keywords=laravel+up+and+running&qid=1558173315&s=books&sprefix=laravel+up+and%2Cstripbooks-intl-ship%2C238&sr=1-1-fkmrnull

The issue is

now() + INTERVAL '1 MONTH'

The query should look more like this.

SELECT * 
FROM mydb 
WHERE creationdate BETWEEN "2011-01-01" 
                   AND DATE_ADD("2011-01-01", INTERVAL 6 MONTH) - INTERVAL 1 DAY
GROUP BY MONTH(creationdate);

Try this

https://www.getastra.com/kb/knowledgebase/how-to-install-sqlite-for-php-on-my-apache-nginx-server/

Change the server tag to env and it should work again.

The code looks like it should work.

I suggest doing a dd on $country and see if both paths are defined and then check that the files are named correctly. It could be as easy as the filename is in the wrong case.

Make your phpunit.xml look like this

<?xml version="1.0" encoding="UTF-8"?>
<phpunit backupGlobals="false"
         backupStaticAttributes="false"
         bootstrap="vendor/autoload.php"
         colors="true"
         convertErrorsToExceptions="true"
         convertNoticesToExceptions="true"
         convertWarningsToExceptions="true"
         processIsolation="false"
         stopOnFailure="false"
         printerClass="Codedungeon\PHPUnitPrettyResultPrinter\Printer">
    <testsuites>
        <testsuite name="Feature">
            <directory suffix="Test.php">./tests/Feature</directory>
        </testsuite>

        <testsuite name="Unit">
            <directory suffix="Test.php">./tests/Unit</directory>
        </testsuite>
    </testsuites>
    <filter>
        <whitelist processUncoveredFilesFromWhitelist="true">
            <directory suffix=".php">./app</directory>
        </whitelist>
    </filter>
    <php>
        <env name="APP_ENV" value="testing"/>
        <env name="TELESCOPE_ENABLED" value="false" />
        <env name="BCRYPT_ROUNDS" value="4"/>
        <env name="CACHE_DRIVER" value="array"/>
        <env name="SESSION_DRIVER" value="array"/>
        <env name="QUEUE_DRIVER" value="sync"/>
        <env name="MAIL_DRIVER" value="array"/>
        <env name="DB_CONNECTION" value="sqlite"/>
        <env name="DB_DATABASE" value=":memory:"/>

    </php>
</phpunit>

You can do that by only having the rules that are common between your store and update methods. Then in the store method you send additional rules into it.

Below is how I did it for a project.

protected function validateBook(Request $request, $validationRules = [])
    {
        $rules = array_merge([
            'title' => 'required',
            'series' => 'required',
            'part' => [
                'required_unless:series,Standalone',
                'numeric',
                'nullable'
            ],
            'format_id' => 'required|exists:formats,id',
            'genre_id' => 'required|exists:genres,id',
            'isbn' => [
                'required',
                'regex:/^(97(8|9))?\d{9}(\d|X)$/'
            ],
            'released' => ['required', 'integer', 'between:1800,' . Carbon::now()->addYear(1)->year],
            'reprinted' => ['nullable', 'integer', 'between:1800,' . Carbon::now()->addYear(1)->year],
            'pages' => 'required|integer',
            'blurb' => 'required'
        ], $validationRules);

        return $request->validate($rules);
    }

Not really an issue you compare today's date with the the end date of the subscription. You can use Carbon for that https://carbon.nesbot.com/docs/#api-comparison

And if end date is greater than today's date it's a valid subscription.

There seems to be a permission issue Permission denied

Try appending sudo to your command.

sudo brew services restart mysql

I'd probaly have a table called subscription_user and in it you have a column called valid_to and then check against it if the difference between them with carbon and if the diff is positive it's a valid subscription and if it's not it's invalid.

There is a new series regarding queues and workers which you should check to see how to use them.

https://laracasts.com/series/queue-it-up

Check the fallback route

https://laravel.com/docs/5.8/routing#fallback-routes

Route::fallback(function () {
    //Send to 404 or whatever here.
});

I went from monthly to yearly last summer and it worked like this

1. The ongoing subscription was canceled
2. The amount for the remaining period was deducted from the new subscription cost.

It probably works the same way with team subscriptions.

I would not use a cron for that.

I would add something like this in the master layout

@auth

    @if(Auth()->user->showSubcriptionNotice())
        Hey man, only  {{ Auth()->user->subscription->daysLeft() }} days left on your subscription.
    @endif
@endauth

As for the mail you should use a queue worker that checks all your users to see which has 5 or less days left.

Try changing

return view('/home')->with(compact('profilelist'));

to

`` return view('/home', compact('profilelist'));

Probably but since you want to do it with Vue and possibly Vue components I advise against it and recommend using regular html in your components.

@devfrey Good eyes but wrong suggestion.

The id should never ever be added with code, the database should always increment it that way it will never be a duplicate.

Or you can use Laravel Telescope

https://laravel.com/docs/5.8/telescope

This error is thrown since you are not removing the created user after each test. So when the test tries to create the user it already exists thus the error.

I suggest you use an in memory database for your testing. The other way is to have a teardown in your test class.