Eloquent Custom Table Name in Model

Level 11

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class Brand extends Model
{
    // Set the table name
    protected $table = $current_store . '_brand';
}

@tuyenlaptrinh you can set the table name direct in model itself using this. but here you have not mentioned more details. so try to find and replace $current_store variable value in the above snippet and test it. Hope it works. Let me know your feedback.

Level 80

@hupp That will throw an exception. You can’t use variables when setting a class property value like that.

Level 1

@hupp Thank you for quick response. I got your idea. But how to pass $current_store to Model. We can not use function in class variable like this

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class Brand extends Model
{
	$current_store = app('current_store');
    // Set the table name
    protected $table = $current_store . '_brand';
}

This is begin project and in an ideal. I am looking solution for this

jaseofspades88

Level 51

Why? It would be easier to have a column on your brands table to differentiate, perhaps type or something that suits your business need. One model, one table is generally considered the best practice, otherwise you're opening yourselves up to all manner of complications.

Level 80

@tuyenlaptrinh You don’t need “prefixes”, because that’s just going to become a pain in the ass to manage. If you have 100 stores, then you’re going to have to run migrations on as many tables, and what happens if the migrations fail part-way through? Your database is going to be left in a horrific, inconsistent state.

Instead, just use a relation. Create a model (and table) for stores, and then have a store_id foreign key in your brands table that connects that brand to a store. Or create a many-to-many relation and brand_store pivot table if a brand should be linked to multiple stores.

Level 1

Thank you @jaseofspades88 and @martinbean . My idea is like this

Store A:
- Warehouse A: 45000 products
- Warehouse B: 50000 products
- Warehouse C: 50000 products.
Store B:
..........

If I have 1000 stores. It will be increase products table maybe 5 millions - 20 millions products and It make slow in query.

I want to separate tables for per store

Level 80

@tuyenlaptrinh You do know relational databases like MySQL and PostgreSQL were literally created to hold millions and millions of rows, right…?

Level 1

@martinbean I know. But want to fast query. I am using one database with 3 millions records and It take more than 5 seconds for search records in table

Level 80

@tuyenlaptrinh So index your data properly.

Level 1

Thanks for all replies. @martinbean @hupp @jaseofspades88 @martinbean I got solution for this. I will make one middleware before request for set table prefix and define it.

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;

class Brand extends Model
{
    use HasFactory;
    protected $table = _PREFIX_DB_.'brands';
}

psrz

https://codebrisk.com/blog/a-useful-laravel-package-to-easily-work-with-mysql-partition

Level 10

@tuyenlaptrinh

Have you checked mysql partitions ?

1 like

Level 1

@psrz Wow. I did not check that before. Thank you

Snapey

Level 122

@tuyenlaptrinh just learn about indexing and use a scope

As Martin says, you have chosen the most complicated and least maintainable solution

hupp