Tray2

I use the fetch api instead of the old way with xmlhttprequest.

async function getRequest(url, parameters = {}) {
  try {
      showLoading();
      let responsePromise = await fetch(connectionString + url, { method: 'GET', headers: parameters});
      if(! responsePromise.ok) {
          hideLoading();
          throw new Error(responsePromise.status );
      }
      hideLoading();
      return await responsePromise.json();
  } catch (error) {
      return error;
  }
} 

I call the function like this

async function isUrgent() {
  const params = {
      'partno': partInfo.partno,
      'trailer_id': activeMasterLabel.trailer_id,
      'truck_id': activeMasterLabel.truck_id
  };

  const response = await getRequest('/endpoint', params);

  if (response.message != null) {
    showAlert(`Could not check if part is urgent (${ response.message })`);
  } else {
    return (response.urgent != 0);
  }
}

The connection string is a global variable in this case but that can easily be a parameter sent in or even hardcoded

I would go with a single users table and then have user roles.

There are several ways of doing that.

1. Add the role directly to the users table.
2. Add a foreign key to the users table and have a roles table
3. Use a pivot table to join the user and the role together.

Option 1 should only be used in a system with very few users.

id | username | role
-------------------------------------
1  | user1       | admin
-------------------------------------

Option 2 is for systems with many users

id | username | role_id
-------------------------------------
1  | user1       | 1
-------------------------------------

The role_id references the roles_table

id | role
---------------
1  | admin
---------------

Option 3 is for multi user systems with a possibility to let a user have multipple roles

Users table

id | username 
-------------------
1  | user1       
-------------------

roles table

id | role
---------------
1  | admin
---------------

role_users table

user_id| role_id
-------------------------------------
 1       | 1
-------------------------------------

The other upside to option 3 is that you can use the provided migrations and authentication out of the box.

Try using this instead

/**
     * @test
     * @dataProvider protectedRoutesProvider
     * @param $method
     * @param $route
     */
    public function guests_are_redirected_to_login($method, $route)
    {
        $response = $this->$method($route);
        $response->assertLocation('/login');
    }

And the dataprovider

public function protectedRoutesProvider()
{
    return [
      'A guest is not authorized to visit the admin page' => ['get', '/admin'],
   ];
}

I'm guessing MySQL, this should most likely work.

Be aware that it's not a good practice to disable constraints. They are there to help you keep data concistency.

//Disable
DB::statement('SET FOREIGN_KEY_CHECKS=0;');

//Enable
DB::statement('SET FOREIGN_KEY_CHECKS=1;');

https://tableplus.com/blog/2018/08/mysql-how-to-temporarily-disable-foreign-key-constraints.html

I'm guessing MySQL, this should most likely work.

Be aware that it's not a good practice to disable constraints. They are there to help you keep data concistency.

//Disable
DB::statement('SET FOREIGN_KEY_CHECKS=0;');

//Enable
DB::statement('SET FOREIGN_KEY_CHECKS=1;');

https://tableplus.com/blog/2018/08/mysql-how-to-temporarily-disable-foreign-key-constraints.html

Check this guide

https://www.howtoforge.com/centos-apache-config-virtual-host

Check this guide

https://www.howtoforge.com/centos-apache-config-virtual-host

@bugsysha Agreed.

I used this blogpost as a starting point

https://tighten.co/blog/tidying-up-your-phpunit-tests-with-data-providers/

Dataproviders is also a good tool to keep the tests cleaner

For example this test checks that a guest is redirected when trying to use any of the routes that needs a logged in user.

<?php

namespace Tests\Feature\Http;

use Tests\TestCase;

class AuthorizationTest extends TestCase
{
    public function protectedRoutesProvider()
    {
        return [
          'Artists: a guest is not authorized to visit the create page' => ['get', '/artists/create'],
          'Artists: a guest is not authorized to visit the edit page' => ['get', '/artists/1/edit'],
          'Artists: a guest is not authorized to visit the store page' => ['post', '/artists'],
          'Artists: a guest is not authorized to visit the update page' => ['put', '/artists/1'],
          'Artists: a guest is not authorized to visit the delete page' => ['delete', '/artists/1'],

          'Authors: a guest is not authorized to visit the create page' => ['get', '/authors/create'],
          'Authors: a guest is not authorized to visit the edit page' => ['get', '/authors/1/edit'],
          'Authors: a guest is not authorized to visit the store page' => ['post', '/authors'],
          'Authors: a guest is not authorized to visit the update page' => ['put', '/authors/1'],
          'Authors: a guest is not authorized to visit the delete page' => ['delete', '/authors/1'],

          'Books: a guest is not authorized to visit the create page' => ['get', '/books/create'],
          'Books: a guest is not authorized to visit the edit page' => ['get', '/books/1/edit'],
          'Books: a guest is not authorized to visit the store page' => ['post', '/books'],
          'Books: a guest is not authorized to visit the update page' => ['put', '/books/1'],
          'Books: a guest is not authorized to visit the delete page' => ['delete', '/books/1'],

          'Formats: a guest is not authorized to visit the create page' => ['get', '/formats/create'],
          'Formats: a guest is not authorized to visit the edit page' => ['get', '/formats/1/edit'],
          'Formats: a guest is not authorized to visit the store page' => ['post', '/formats'],
          'Formats: a guest is not authorized to visit the update page' => ['put', '/formats/1'],
          'Formats: a guest is not authorized to visit the delete page' => ['delete', '/formats/1'],

          'Genres: a guest is not authorized to visit the create page' => ['get', '/genres/create'],
          'Genres: a guest is not authorized to visit the edit page' => ['get', '/genres/1/edit'],
          'Genres: a guest is not authorized to visit the store page' => ['post', '/genres'],
          'Genres: a guest is not authorized to visit the update page' => ['put', '/genres/1'],
          'Genres: a guest is not authorized to visit the delete page' => ['delete', '/genres/1'],

          'Records: a guest is not authorized to visit the create page' => ['get', '/records/create'],
          'Records: a guest is not authorized to visit the edit page' => ['get', '/records/1/edit'],
          'Records: a guest is not authorized to visit the store page' => ['post', '/records'],
          'Records: a guest is not authorized to visit the update page' => ['put', '/records/1'],
          'Records: a guest is not authorized to visit the delete page' => ['delete', '/records/1'],

          'Tracks: a guest is not authorized to visit the create page' => ['get', '/tracks/create'],
          'Tracks: a guest is not authorized to visit the edit page' => ['get', '/tracks/1/edit'],
          'Tracks: a guest is not authorized to visit the store page' => ['post', '/tracks'],
          'Tracks: a guest is not authorized to visit the update page' => ['put', '/tracks/1'],
          'Trackss: a guest is not authorized to visit the delete page' => ['delete', '/tracks/1'],

          'BookCollection: a guest is not authorized to visit the store page' => ['post', '/bookcollections'],
          'BookCollection: a guest is not authorized to visit the delete page' => ['delete', '/bookcollections/1'],

          'BookRead: a guest is not authorized to visit the store page' => ['post', '/books/read'],
          'BookRead: a guest is not authorized to visit the delete page' => ['delete', '/books/read/1'],


        ];
    }

    /**
     * @test
     * @dataProvider protectedRoutesProvider
     * @param $method
     * @param $route
     */
    public function guests_are_redirected_to_login($method, $route)
    {
        $response = $this->$method($route);
        $response->assertLocation('/login');
    }
}

My guess is that something else is locking that record.

I suggest you try doing a select from update no wait skip locked then it will skip the update otherwise it will hang until the update is made.

http://www.dba-oracle.com/t_select_update_skip_locked.htm

You can run this to see what is locking your table

select * from DBA_DDL_LOCKS where name like :your_table;

My guess is that something else is locking that record.

I suggest you try doing a select from update no wait skip locked then it will skip the update otherwise it will hang until the update is made.

http://www.dba-oracle.com/t_select_update_skip_locked.htm

You can run this to see what is locking your table

select * from DBA_DDL_LOCKS where name like :your_table;

It sound to me that you have a very old computer and a really slow internet connection. I suggest you try closing as many applications as possible just to see if it runs a bit faster.

It might be that you have a shitload of processes running at the same time preventing the composer from running.

As a rule of thumb, never ever use {!! $variable !!} unless you really can trusts the source and actually avoid it even if you can.

I'm guessing this is a blog or somewhere you allow tha user to input html into the database.

I would go with Markdown instead of html so I wouldn't have to worry as much about the user breaking the page.

Laravel by default escapes html before storing it in the table.

What happends if you change this line

$user = User::findOrFail($id);

To

$user = User::find($id);
dd($user);

Is the $user null or is it a user collection?

Are you talking about storing the exceptions as a log or store the error messages in the database instead of in your code?

You use CSS for that just like you wold do for any webpage.

Use the developer tools in your browser and check what uri it's giving the 404 on. It's most likely not pointing to the same uri as your postman request.

First of all I would never store a many to many relationship in a json field.

Store it in a pivot table instead then you can search and use aggregate functions on the data without any issues.

The pivot table can look something like this.

• student_id
• course_id
• grade

I'm not a big fan of json columns at all since they kinda defeat the purpose of a relational database. They are also imho a shortcut to bad database designs.

According to the packagist page it does support Laravel 6 and 7.

https://packagist.org/packages/harrygulliford/laravel-firebird

I suggest you start here

https://github.com/harrygulliford/laravel-firebird

And if that doesn't help you show us some code and the error messages you have.

It seems that firebird does not allow boolean columns in the database or at least not with a default value. I suggest you change these two lines

$table->boolean('all_branch')->default(false)->comment('access all branch');
$table->boolean('is_active')->default(true);

To

$table->char('all_branch', 1)->default('0')->comment('access all branch');
$table->char('is_active', 1)->default('1');

According to the packagist page it does support Laravel 6 and 7.

https://packagist.org/packages/harrygulliford/laravel-firebird

I suggest you start here

https://github.com/harrygulliford/laravel-firebird

And if that doesn't help you show us some code and the error messages you have.

Like I said that has nothing to do with the code. It all depends on the network and every server on the way from your server to the destination. Sometimes it can be fast other times slow. It all depends on the route it takes and how high the load is.

You can create your own custom error messages.

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

That has nothing to do with the code it self. It depends on the network and the servers running.

You say that you using dummy data, why not make sure you have a relationship and then try to drop it.

I would not replace them but rather remove them.

https://www.w3schools.com/php/func_string_strip_tags.asp

I updated my previous reply since I was wrong in the effect of constraints when doing DDL.

Make sure that it is the cli php.ini you made the changes to and not the cgi php.ini used by your server.

There are two different languages in SQL, DDL or Data Definition Language and DML or Data Manipulation Language. With DDL you create, alter, truncate and drop database objects (tables, views, indexes and such). With DML you read, insert, delete and update records in the database.

To prevent any object from being dropped you can create a user that only has SELECT, INSERT, UPDATE and DELETE on the tables in the database.

https://www.youtube.com/watch?v=HzZ3h-COam4

My bad. If there is a foreign key constraint and one record is referencing it you can't drop the table being referenced.

ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails

However you can drop the table that contains that foreign key.

Have you tried felixfbecker.php-intellisense?

In the path variable you never specify the file name, just the directory that contains the file.

So this

C:\Batch\homestead.bat

Should be this

C:\Batch

That is of course if your files are in that directory.

In your case I would use markdown for the blogposts then you can use something like this to find your page breaks.

<div style="page-break-after: always"></div>

As the error message states you don't have the correct privileges to create a database.

If you want to move the data from one database to another you need to export it.

Not knowing what RDBMS you are using I can't point you to any guide on how to do that.

If it's just the database structure I recommend using Laravel migrations. If it's just a few tables with a few records in each that has default values use seeders for those.

You can do something like this

\DB::select("SELECT COLUMN_COMMENT FROM INFORMATION_SCHEMA.COLUMNS WHERE  TABLE_SCHEMA = '<your database>' AND TABLE_NAME = '<your table>' AND COLUMN_NAME = 'your column'");

When the deploy to the server is finished.

Because after deploy you should run composer install to install all the dependencies,

Yes you can retreive it but I wouldn't use comments in my application like that.

You can always just do a regular select on it.

I'm guessing you are using MySQL 8 which has updated the security hash when it comes to passwords.

Try running this command in you database tool

ALTER USER username IDENTIFIED WITH caching_sha2_password BY 'YOUR_PASSWORD';

Why would you want to do that?

What you could do is create a table called genders.

gender   | description
--------------------------------
m        | male
f        | female
o        | other

Then use the gender as the primary and foreign key in your table if you want a description of the abbriviation.

In the path variable you never specify the file name, just the directory that contains the file.

So this

C:\Batch\homestead.bat

Should be this

C:\Batch

That is of course if your files are in that directory.

Just add the ->comment('my comment') in your migration file

$table->string('name')->comment('The full name of the user');

https://laravel.com/docs/7.x/migrations#column-modifiers

imho = In My Humble Opinion.

With the proper indexes 1.6M rows is not a problem and from reading your description I find it highly unlikely that all 400 users customizes all of their elements.

If indexes shouldn't be enough you can partition the table.

imho = In My Humble Opinion.

With the proper indexes 1.6M rows is not a problem and from reading your description I find it highly unlikely that all 400 users customizes all of their elements.

If indexes shouldn't be enough you can partition the table.

Have you tried felixfbecker.php-intellisense?

If you exchange the single quotes for double you should be able to do this.

$table->string('name')->comment("The full name of the user\nThis is row two");

Then please mark the reply as best.

Just add the ->comment('my comment') in your migration file

$table->string('name')->comment('The full name of the user');

https://laravel.com/docs/7.x/migrations#column-modifiers

https://laratrust.santigarcor.me/docs/6.x/usage/seeder.html

Remeber that when you encrypt the database fields it will require decryption every time you access the values and it complicates things when you need to do basic searches in your queries. It will slow down your appliction.

You foreing keys must be the same typr as the id they are referencing.

Change them to either foreign or unsignedBigInteger

$table->unsignedBigInteger("organization_id");

$table->foreignId("organization_id");

https://laravel.com/docs/7.x/migrations#foreign-key-constraints