Tray2

Look like there are a few full table scans in this one.

I suggest you do an explain plan and look for them. Add indexes where they are it might help. I would also see which part of the query that takes the most time and place that last.

Are you using blade or vanilla PHP?

Blade

@foreach($somethings as $something)
    {{ $something->field }}
@endforeach

Vanilla

<?php
 foreach($somethings as $something) {
    echo $something['field'];
}

Do you have the proper permissions to your storage folder?

Transaction::whereRaw('plan_price - final_price >= 5');

Should work.

Something like

$view = model::where('field', 'condition')->first()
$view->pageviews++;
$view->update();

Should work.

Not knowing anything about you code but I think you have two records in the machines table.

If so you are probably running a query similair to this one.

SELECT da.field, m.field
FROM device_alerts da,
            machines m;

That will give you two rows for each record in table.

To solve this you need to join the tables in your query.

SELECT da.field, m.field
FROM device_alerts da,
            machines m
WHERE da.machine_id = m.id;

What you call the controller is up to you but not all models needs controllers. I suggest however to follow the naming conventions in Laravel.

Model are named The same as the table but in singular ie posts table has a model named Post Controllers are named after the table, so posts table will become PostController or PostsController (singular or plural is optional here).

Not sure what you mean exactly but if you have the correct relationships set up you can do something like this

@foreach($forms as  $form)
  <a href="/forms/{{ $form->id }}">{{ $form->question }}</a><a href="/forms/{{$form->subsection_id }}">{{ $form->subsection->question }}</a>

@endforeach

If you have something like

public function index()
{
  $customers = Customer::all();
  return view('customer.index', compact('customers'); 
}

In your controller and

public function address()
{
  return $this->hasOne(CustomerAddress::class);
}

In your Customer model you can

{{ $customer->address->zip }}

In your view

There seems to be a limitation on how long the constraint name can be.

I haven't tried it but in most places it's possible to override the default naming so something like

$table->unique([], 'index_name');

might work.

Are you uploading a new file? If so make sure you have set the form to multipart.

Do some poor man debugging by dd($request);too mke sure the file is passed.

According to Microsoft the Azure SQL is basically the latest stable version of SQL Server so switching should not be that hard.

https://docs.microsoft.com/en-us/azure/sql-database/

You could probably get away with just changing your env file to use sql server.

https://barryvanveen.nl/blog/39-connect-to-mssql-database-from-php

Then you probably should check on how to set up a subdomain and how to reroute to it.

Sounds a bit like you hace problems with your document root. If you are running Apache check out .htaccessand how to reroute everything to your public folder.

https://stackoverflow.com/questions/23635746/htaccess-redirect-from-site-root-to-public-folder-hiding-public-in-url

A quick search revieled this https://docs.microsoft.com/en-us/azure/app-service/containers/tutorial-php-mysql-app I hope that is something as to what you are looking for.

A matter of style and or taste imho.

Simple queries like

$books = Book::all();

I would place in the controller but more complex 5+ lines or so I might consider moving to the model.

Since I try to keep my eloquent as simple as possible I move the more complex stuff into database views.

The serverside builds the page from your includes so a simple view source in your browser will give you everything.

Without any code it's a bit hard to see what goes wrong but you need to load the javascript last to make sure that all the elements that you use are in place.

The first thing I'd do is add some indexes to those tables and I think you could shave of at least 50% of the time there. You can run explain plan to see where it uses full table access and add the indexes there. You will also probably see which part of the query takes most of the time and then you can put that last so you have the smallest possible selection to run it on.

I would also make sure that any carthesian products are removed since they are usually bad for performance.

You need Javascript for that as far as I know.

Docblocks are optional and the same goes for typehints. You don't really need them but some argue that you always should use docblocks and or typehints and some argue against it.

It all comes up to personal preferences unless of course there is a standard at the company or project that says you should use one or both.

This is a guide should help you.

https://medium.com/@vineeth030/laravel-confirm-dialog-for-delete-button-5976554d839

Check diffForHumans https://carbon.nesbot.com/docs/#api-humandiff

Do a ddon them both and you will probably see the problem.

I haven't tested it but when you make your settings you don't have an idand you don't have created_atand updated_at all of which you most likely have when you call $user->settings.

On the individual server. The load balancer is only like a traffic cop deciding which road your request should take.

The problem seems to be in your updateAdjustment method

Probably this line

DB::table('adjustments')->where([ ['fromPID','=',$chunks[$i][0]] , ['toPID','=',$chunks[$i][1]], 'on','=',$chunks[$i][2]], ['at','=',$chunks[$i][3]] ])->update(['status' => $chunks[$i][4]]);

<form action="" method="">
<button onclick="yourFunctionHere()" class="btn_back" name="btn_back">
</form>

Why use a button when it seems to be a normal link?

Why not just ask them for their email when they upload the image?

500 errors means that there is something wrong at the backend and not the frontend so show your controller code for that route.

Like stated before you need to initiate $pushin the top of your function

public function getStuff(Request $request)
{
     $push = '';

     //your code here
}

Read about variable scopes

https://www.php.net/manual/en/language.variables.scope.php

https://api.jquery.com/submit/

You need to do a post request where you pass the data from your form to your controller.

THis should give you some guidience https://www.johnmorrisonline.com/jquery-tutorial-submit-a-form-and-post-data-using-jquery-and-ajax/

$request->validate(['title' => 'unique:courses']);

Is how I would do it.

You can temporarly disable the unique indexes SET UNIQUE_CHECKS=0;.

How often is this updated? If the answer is more than once a day I suggest that you remove the constraint from your table.

It seems that the fade in is run at least twice instead of once and that might be the issue.

SQL optimization is always tricky but usually moving the heaviest lifter (in this case the between) last usually helps a bit.

What you can try is to move older records to another table, let's say everything older than three months and then build check if the dates are in which table and build the query dynamically.

Then it should use an index.

However I would move the between condition last since it probably gives the biggest span just to test.

Unless there is a huge difference in execution times I wouldn't worry about it since the MySQL parser is probably smarter than both you and me. It will choose the best plan it can. :)

1. A show can have many seasons
2. A season can have many episodes
3. An episode can only belong to one season
4. A season of one show can only belong to one show

I would probably not have a seasons table since it would only be filled with the show number and the season number. I would put the season in the episodes table to start with but that is up to you.

Vim is an awesome editor that takes some time to master fully but once you do ....

There is a really good course here on how to configure it.

https://laracasts.com/series/vim-mastery

Have you removed the phar extension on the composer file?

If not you should be able to use the same trick and the run php <path to composer>/composer.phar. I haven't tried but it should be a plausible workaround.

There is a validation that you could use required_if https://laravel.com/docs/5.8/validation#rule-required-if

Otherwise you can always check if which value is set and then validate it.

if (isset($request->get('this_id')) &&  !isset($request->get('that_id'))) {
    //validate this_id
} else {
    //validate that_id
}

However it's not neccesarry to split them up since you should pass them both all the time and it will update if needed.

You do that in your view.

<a href="/movies/{{ $movie->id }}">{{ $movie->title }}</a>

And so on.

I assume this is $ we are talking then storeit as cents and as Nash pointed out use number_format.

Some code maybe?

I would also go with adding a new drive then mount it to the proper directory.

Something like this?

https://stackoverflow.com/questions/15201071/how-to-get-full-path-of-selected-file-on-change-of-input-type-file-using-jav

Yes they can but that is not the issue. The issue is load times.

First your server must the fast enough to get the data and parse the view for you.

Let's sat each row is 500 bytes with a template of 20Kb. That would make the page about 605Kb. This needs to be send over the network and some users are still on really slow connections.

Then depending on your structure of the page and the styles used and any javascript you have on your page will make the rendering time increase.

So I suggest you try at some site that helps you with this.

Here are some examples

https://serps.com/library/how-to-measure-your-website-speed-and-load-times/

Check this thread https://laracasts.com/discuss/channels/laravel/laravel-55-disable-auto-login-after-registration

Have you checked this https://laravel.com/docs/5.8/verification ?