Froilan Cerna Ventura's questions

good night.

I am configuring a project with spatie/multitenancy and when configuring the User model to authenticate and login, I add the UsesTenantConnection trait to the User model, the authentication is successful for the tenants, but for the owner it does not recognize the connection. If I use the UsesLandlordConnection trait or neither of the two traits in the User model, when logging in, whether in the owner or in the tenants, it recognizes the connection of the owner, and in the owner it is accessed without problems, for the owner it is fine, but for the tenants it shows a message of incorrect credentials, because it is considering the connection of the owner.

Here is the error that I get when I use the UsesTenantConnection trait and login to the owner.

Illuminate\Database\QueryException
SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected (SQL: select * from `users` where `email` = [email protected] limit 1)

http://multitenancy_spatie.test:82/login

And here the relevant configuration files

in the kernel

protected $middlewareGroups = [
    'tenant' => [
        \Spatie\Multitenancy\Http\Middleware\NeedsTenant::class,
        \Spatie\Multitenancy\Http\Middleware\EnsureValidTenantSession::class,
    ]
];

config('database')

[
 "default" => "landlord",
 "connections" => [
   "tenant" => [
     "driver" => "mysql",
     "url" => null,
     "host" => "127.0.0.1",
     "port" => "3306",
     "database" => null,//Tenant Autr
     "username" => "root",
     "password" => "",
     "unix_socket" => "",
     "charset" => "utf8mb4",
     "collation" => "utf8mb4_unicode_ci",
     "prefix" => "",
     "prefix_indexes" => true,
     "strict" => true,
     "engine" => null,
     "options" => [],
   ],
   "landlord" => [
     "driver" => "mysql",
     "url" => null,
     "host" => "127.0.0.1",
     "port" => "3306",
     "database" => "multitenancy_spatie",
     "username" => "root",
     "password" => "",
     "unix_socket" => "",
     "charset" => "utf8mb4",
     "collation" => "utf8mb4_unicode_ci",
     "prefix" => "",
     "prefix_indexes" => true,
     "strict" => true,
     "engine" => null,
     "options" => [],
   ],
 ],
]

config('multitenancy')

[
 "tenant_finder" => "Spatie\Multitenancy\TenantFinder\DomainTenantFinder",
 "tenant_artisan_search_fields" => [
   "id",
 ],
 "switch_tenant_tasks" => [
   "Spatie\Multitenancy\Tasks\SwitchTenantDatabaseTask",
 ],
 "tenant_model" => "Spatie\Multitenancy\Models\Tenant",
 "queues_are_tenant_aware_by_default" => true,
 "landlord_database_connection_name" => "landlord",
 "current_tenant_container_key" => "currentTenant",
 "actions" => [
   "make_tenant_current_action" => "Spatie\Multitenancy\Actions\MakeTenantCurrentAction",
   "forget_current_tenant_action" => "Spatie\Multitenancy\Actions\ForgetCurrentTenantAction",
   "make_queue_tenant_aware_action" => "Spatie\Multitenancy\Actions\MakeQueueTenantAwareAction",
   "migrate_tenant" => "Spatie\Multitenancy\Actions\MigrateTenantAction",
 ],
 "queueable_to_job" => [
   "Illuminate\Mail\SendQueuedMailable" => "mailable",
   "Illuminate\Notifications\SendQueuedNotifications" => "notification",
   "Illuminate\Events\CallQueuedListener" => "class",
   "Illuminate\Broadcasting\BroadcastEvent" => "event",
 ],
]

.env file

APP_NAME=Laravel
APP_ENV=local
APP_KEY=base64:millave
APP_DEBUG=true
APP_URL=http://multitenancy_spatie.test:82

DB_CONNECTION=landlord
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=multitenancy_spatie
DB_USERNAME=root
DB_PASSWORD=

Routes file -> routes/web.php

Route::domain('{tenant}.multitenancy_spatie.test')->middleware('tenant')->group(function() {
    // routes
    Route::get('/', function () {
        return view('auth.login');
    });
    Route::middleware(['auth:sanctum', 'verified'])->get('/dashboard', function () {
        return view('dashboard_tenant');
    })->name('dashboard');
});

Route::domain('multitenancy_spatie.test')->group(function() {
    // routes
    Route::get('/', function () {
        return view('welcome');
    })->name('home');
    
    Route::middleware(['auth:sanctum', 'verified'])->get('/dashboard', function () {
        return view('dashboard');
    })->name('dashboard');
});

I have reviewed on github: https://github.com/spatie/laravel-multitenancy/issues/224 , in that issue they deal with the same error, but I have not been able to find the solution to start the session.

Thanks for your help.

Hello good evening.

I have a doubt, regarding the indexes, it is for both managers, SQL and MySQL.

I have a Persons Table , in which two types are saved, client or supplier , and the records are stored according to the order in which they are entered. When creating the table the order is by the Primary Key . But I want to avoid performing "order by supplier_type, number, name" but it is already defined in this way.

How could I structure the table so that it is already ordered and the search is easier and faster?

What I want to achieve is something like this with indexes, whether in ascending or descending order, without the need to use order by, with unique if it can be done, but with non-clustered indexes, which supposedly work to make the query more efficient, they don't. I have accomplished.

order by supplier_type, number, name

order by supplier_type, number desc, name

Table with the index of the Primary Key

Table with the created index, remains unchanged

Table with Unique constraint, sort by type of person, number and name, which is the order I want my table structure to have, but I don't want to use Unique in this table

I have read that database indexes work like the index of a book and return queries more efficiently, but honestly I don't see the reason how they really work.

I have always optimized my queries without indexes and have worked with up to 100,000 records, with more than 40 columns, although the best efficiency I achieved was 2 seconds. In some cases, it has helped me to have structured the table well, to have correctly defined the data types, the lengths, to correctly relate the joins, and other times the Unique restrictions, which solved the problem because it was the order that was needed and they coincided with the requirement. to restrict registration based on those fields.

Good evening, my question is the following.

I am using datatables to load a list into a table and I am also using the export properties. For the latter it is that I have problems, what happens is that I do not want the title to appear in the first row of the sheet of my exported excel document.

//este codigo me imprime en la primera fila el titulo y es lo que no quiero
dom: 'Bfrtip',
buttons: [
    {
        extend: 'excel',
        text: '<i class="fa fa-file-excel-o"></i>&nbsp;&nbsp; Exportar a Excel',
        title: 'Mi Titulo',
    }
],

//Use este codigo en reemplazo, me soluciona el problema pero me genera otro
//Que es el de la imagen, no tengo problemas al recuperar, porque me muestra
//todos los datos sin excepcion, pero es tedioso para el usuario tener que 
//abrir el archivo y salga siempre ese mensaje
dom: 'Bfrtip',
buttons: [
    {
        extend: 'excel',
        text: '<i class="fa fa-file-excel-o"></i>&nbsp;&nbsp; Exportar a Excel',
        filename: 'Mi Titulo',
        title: ''
    }
],

Seeing the problem is in the 'title' attribute , even if they put empty quotes or a value equal to null, this problem persists.

Good night.

Thanks for the collaboration.