Tray2

One migration per table as long as the project isn't launched then after that one for each changed table and release itteration.

You can probably make some changes and structure the migration files.

Something like

• Migrations/Base Tables
• Migration/Table Updates
• Migration/Table Indexes

Or something similar of a single folder is getting too messy

You can always try git clone https://github.com/laravel/laravel.git

Have you checked this https://laravel.com/docs/7.x/views#sharing-data-with-all-views

table->id() is a bigInteger so all your foreign keys needs to be the same format.

Schema::table('posts', function (Blueprint $table) {
    $table->unsignedBigInteger('user_id');

    $table->foreign('user_id')->references('id')->on('users');
});

You can use other selectors than id

https://www.w3schools.com/cssref/css_selectors.asp

Have you checked this https://laravel.com/docs/7.x/views#sharing-data-with-all-views

Have you tried

path/to/php73 ./composer.phar create-project laravel/laravel <project name> ?

Something like that yes.

@snapey didn't know those existed, thanks for the heads up.

I'm guessing you are using aja to send the form so you most likely need to prevent default behaviour on your Save button which I guess is a submit button.

table->id() is a bigInteger so all your foreign keys needs to be the same format.

Schema::table('posts', function (Blueprint $table) {
    $table->unsignedBigInteger('user_id');

    $table->foreign('user_id')->references('id')->on('users');
});

Either change your comlumn type to decimal or add quotes in the migration.

'planned_advance_payment' => '0.29',

You OrdersController needs to use the order number and the hash to be retrieved from the database.

 public function show(Request $request)
    {
        
        return view('qr.confirm-order')->with(['order'=>Order::where('purchase_num', $request->purchase_num)->where('hash', $request->hash)->get()]);
     
    }

Yes.

An order number might look something like 5155255 and then the hash is to prevent anyone from just changing the order number manually in the url.

The order belongs to a purchase and to connect those you have a purchase_id in your orders table.

Why would you have a purchase_id in your purchase table?

If you use prefixes on your primary key then you would otherwise no.

You really should read up on foreign keys in relational databases.

You need to create the hash when the order is inserted into your orders table.

You should have a purchase_id in the table connected to the model where you have that code.

So in your oders table you should have that column.

Yes you can do that or just use the str::uuid() helper which generates a random unique identifier.

https://yoursite.com/orders/confirm/<the order number>/<the hash> or something similar.

You should display a button to send a post request to confirm.

I updated the route suggested in the previous reply.

Show us your migration files.

There are several ways to do that.

One is to hash let's say the users email and order number

$hash = Hash::make($user->email + $this->orderno);

Or you can use uuid to generate a unique key

$id = Str::uuid();

Then you can use some endpoint like

Route:.get('orders/confirm/{order}/{hash}', '[email protected]');

In my opinion yes. You should almost always match the model with a controller.

You will need a custom validation for that.

https://laravel.com/docs/7.x/validation#custom-validation-rules

My guess is that the first one gives you a cartesian product and the other doesn't.

That basically means that you have duplicates in the first query. It adds all records together regardless of the where clause.

However that is just a guess.

The cors issue is what you get when using localhost. You need to use a proper domain for ajax.

That looks to me like you really need to use the database for what it's made to do instead of using php to process the results.

Simplified example:

PHP side processing

$games = Game::all();
foreach($games as $game) {
	if($game->title == 'Quake') {
		//do something
	}
}

SQL side processing

$game = Game::whereTitle('Quake')->get();
//do something

The first example would most likely generate an 500 error if you have thousands of games in your table and use up way more memory then necessary.

The second example would use the RDBMS to get the data in an efficient memory lean way.

This would work as well

App\Post::latest()->limit(20)->orderBy('views', 'desc')->get();

And if it gets slow you can do

App\Post::latest()->limit(20)->orderBy('views', 'desc')->toSql();

Then you can run explain on your query to see where you need to add your indexes.

Your SQL would look like this

select * from `posts` order by `created_at` desc, `views` desc limit 20;

And with the explain it would look like this

explain select * from `posts` order by `created_at` desc, `views` desc limit 20;

And the result something like this

+------+-------------+---------+------+---------------+------+---------+------+------+----------------+
| id   | select_type | table   | type | possible_keys | key  | key_len | ref  | rows | Extra          |
+------+-------------+---------+------+---------------+------+---------+------+------+----------------+
|    1 | SIMPLE      | posts | ALL  | NULL          | NULL | NULL    | NULL | 3    | Using filesort |
+------+-------------+---------+------+---------------+------+---------+------+------+----------------+

Look for full table scan and try adding indexes to remove those.

My guess is that the first one gives you a cartesian product and the other doesn't.

That basically means that you have duplicates in the first query. It adds all records together regardless of the where clause.

However that is just a guess.

So you are making a post request to https://somedomain.com/auth/register ?

Are you passing a valid CSRF token?

Relational databases will probably never be obsolete but rather there is a time and place for everything.

https://www.integrant.com/when-to-use-sql-vs-nosql/

There are several packages for MongoDB already

https://medium.com/@alexrenoki/when-to-use-nosql-getting-started-with-mongodb-in-laravel-f5376ceaf545

https://github.com/jenssegers/laravel-mongodb

A singleton is mostly used instead of application wide global variable.

A regular browser in the phone would be enough and the need to be signed in isn't mandatory. Though most courier firms have their own system to track shipments.

Show us your routes, controller and blade file.

In short yes it's doable.

The Qr code needs to contain a link to your finish order route with a uuid or similar that puts the order into finish state. You can use something similar to how Laravel handles the reset password link.

Since you are on a mac use Laravel Valet instead of mamp.

https://laravel.com/docs/7.x/valet#introduction

Then you can use a path like the one above.

Where are you installing it?

You should create a folder in your home directory for it something like

/Users/<user>/Code

And in it create your project.

Is the index file named ìndex.blade.php`?

Then the test isn't using the phpunit.xml for some reason.

What happens if you comment out all the sqlite settings in your .env file?

//DB_CONNECTION=sqlite   <--
//DB_HOST=127.0.0.1
//DB_PORT=3306
//DB_DATABASE=/home/my/path/db.sqlite   <--
//DB_USERNAME=root
//DB_PASSWORD=

And run the tests again?

Here is a tutorial for it released this week https://laracasts.com/series/whats-new-in-laravel-7/episodes/6

Try

composer create-project laravel/laravel somedir

It tells composer what to download

Try

composer create-project laravel/laravel somedir

Do you have the right php version installed?

php --version should give version 7.3 or above.

Try this package

https://github.com/Adldap2/Adldap2-Laravel

If you run ./vendor/bin/phpunit does it still empty your sqlite db?

I liked the PHP Object-Oriented Solutions by David Powers isbn 9781430210115

https://www.goodreads.com/book/show/4479421-php-object-oriented-solutions?ac=1&from_search=true&qid=WsFW57sM0N&rank=1

Then the test isn't using the phpunit.xml file but rather your .env file.

Are you sure the sqlite :memory: is ser in your phpunit.xml?

Are you running phpunit in the root of your project?

<server name="APP_ENV" value="testing"/>
<server name="BCRYPT_ROUNDS" value="4"/>
<server name="CACHE_DRIVER" value="array"/>
<server name="DB_CONNECTION" value="sqlite"/>
<server name="DB_DATABASE" value=":memory:"/>
<server name="MAIL_MAILER" value="array"/>
<server name="QUEUE_CONNECTION" value="sync"/>
<server name="SESSION_DRIVER" value="array"/>

When using an Sqlite in memory database and database mirgrations it does the following

1. Migrate the database
2. Perform the test
3. Rollback the database migration done before the test.

PHPUnit uses the phpunit.xml file to know which database to use and it does in your case don't use the one you specified in your .env file. To be able to log in using your browser you need to run php artisan migrate and then add a user so that you can use that to log in.

I would check all the database queries and see if that some indexes are needed. You can use the laravel debubar for this or telescope.

You are probably refering to the Task instance instead of the task->id somewhere but it's hard to guess since you don't share your code.