bugsysha

@michaloravec I guess you will receive the same answer, that "you don't know if it causes any performance issues" :D

Did you check this out? https://github.com/doctrine/dbal/issues/4243

Knowing Laravel, those callbacks are executed only when that command runs so it should not bring any performance decay. But it is true that I do not know that since I always create classes for every command.

Yeah, contacting official Vapor support.

Either some piece of info is missing or you can just use from info and based on that put it into specific thread.

Show your migration.

It is a good use case to use for, but you are overcomplicating things.

You should be able to just typehint the ManageFilters class in the constructor or the method of the controller.

class ThreadController extends Controller
{
  protected ManageFilters $manageFilters;

  public function __construct(ManageFilters $mangeFilters)
  {
    $this->manageFilters = $manageFilters;
  }

  public function index()
  {
    $this->manageFilters->addFilter($filter);
    // ...
  }
}

Or if you only need it in one controller method then:

class ThreadController extends Controller
{
  public function index(ManageFilters $manageFilters)
  {
    $manageFilters->addFilter($filter);
    // ...
  }
}

Have you watched https://laracasts.com/series/whats-new-in-laravel-8/episodes/11

Naming is super confusing... Where is the third model?

Does it really matter? If you care about the performance on that level then maybe you've chosen wrong tech or stack.

Routing depends on the order in which you define them. So if you have something that is being matched when it shouldn't then just place it above.

Yeah, switch to a proper IDE. ST is only a text editor.

You need users relationship on Location model.

If you are OK with the "lag" then no issues there.

But current state can be fetched from the database so no worries there.

Create a job and do it there and just pass that Example object.

https://laravel.com/docs/8.x/queues#creating-jobs

You should not solve such complex problems during weekends/holidays/birthdays :D

You should not solve such complex problems during weekends/holidays/birthdays :D

@snapey it is very common for a developer not being able to explain the issue well cause he does not understand it. He needs guidance, but I do not have the energy right now to do it.

It always turns out to be that the person who wrote that did something wrong.

Sunday mornings seem to be the worst. There has also been recent spates of people creating a profile, reposting someone's existing answer so that it does not look out of place, with the idea of coming back later to insert their spam links.

People. You can't live with them, and yet they're everywhere :D

@automica yeah, I was feeling bit left out so I wanted to give it a try :D

Is it just me or spam discussions and replies count is increasing?

Then your hook deletes it.

Is there anything useful in log files?

On all projects over many years I only had to do it once per project. You probably have something that removes that link.

Not sure about that. It is safer if you look it up so I do not miss something.

You said you want same functionality with same performance. I know that Nova is using Algolia for Geo auto-fill stuff. Maybe your do not mind spending few bucks for excellent search results.

Almost every documentation site is using Alholia these days. Even projects that are not that popular. So maybe it is not charged per letter.

Default light theme. Can't beat the readability of it. Monokai at night.

If that is something specific to the UI I would use browser's Local Storage. But if that is a permanent user setting then I would use database.

How can you have model with multiple tables?

I would go with observers cause they are automatically triggered once the price is updated. No need for repositories, especially cause repositories are not at all a right pattern to use for this problem.

https://laravel.com/docs/7.x/eloquent#observers

Try checking out Algolia search and there are videos here on Laracasts about it.

Put die() instead of sleep() and check.

It seems to me that you are overlooking it. Have you tried it?

But in my server it's so fast and it throw Illuminate/Http/Client/ConnectionException with message 'cURL error 6: Could not resolve host: immediately no matter what is set for timeout

Timeout is not about waiting till it runs out. It is only used when it is having trouble receiving response. If it gets the response that the host does not exists it will exit right away.

Have you tried like it is in the docs?

$response = Http::timeout(3)->get(...);

If it is using transactions then you can not see it in the database. Use DatabaseMigrations if you want to see it in the database.

Firewall or something like that might be restricting access.

Are you using RefreshDatabase or DatabaseTransactions or DatabaseMigrations trait?

Assign different values and see.

@connecteev Valet is local and no VMs required.

Maybe this will help https://reinink.ca/articles/calculating-totals-in-laravel-using-conditional-aggregates

Try Laravel Valet, it can manage PHP versions and switch between them.

You can issue a token that can be used for such scenario.

https://laravel.com/docs/7.x/sanctum#issuing-api-tokens

By multiple rows I guess you mean multiple models? If you queue the action it will execute the code for every selected model. What I've used in this situation is limit the visibility of the action to show it only on details page of the model (hide it from index). Then inside that action I've ignored selected models and just fetched correct models with Eloquent.

If you find some better solution please post it.

They are probably using Laravel Sanctum so maybe check that. Also look it up on YouTube, there are nice explanations.

@jlrdw I would rather go with custom attribute casts than polymorphic relationships, but I just give two suggestions that are better than conditional inside a relationship.

Avoid what @ravish suggested. Either go with polymorphic relationship or with a JSON field with custom casts.

https://laravel.com/docs/7.x/eloquent-relationships#polymorphic-relationships

https://laravel.com/docs/7.x/eloquent-mutators#custom-casts

By multiple rows I guess you mean multiple models? If you queue the action it will execute the code for every selected model. What I've used in this situation is limit the visibility of the action to show it only on details page of the model (hide it from index). Then inside that action I've ignored selected models and just fetched correct models with Eloquent.

If you find some better solution please post it.

public function mantenciones(Request $request){

      $this->validate($request, [
        'fecha-programada_servicio_start'=>'date_format:d-m-Y',
        'fecha-programada_servicio_end'=>'date_format:d-m-Y',
      ]);

      $role=Role::where('name','=','Tecnico')->first();
      $usuarios=$role->users()->select('users.id','users.name')->get();
      $jsonAsignables=$usuarios->pluck('name','id');
$clientes=$this->cliente->all("nombre");


      return view('reportes.mantenciones', ['request' => $request,'jsonAsignables'=>$jsonAsignables, 'clientes'=>$clientes]);
    }

This should work. You should also try to write cleaner code.