Using table prefixes in Laravel?

You can setup table prefix in config/database.php,

    'prefix' => '',

And yes it will prepend the prefix to the table, if you want to set prefix in your .env file you can:

.env

...
DB_TABLE_PREFIX=abc
...

and in config/database.php

    'prefix' => env('DB_TABLE_PREFIX', 'abc')

Thanks for the info. It would be useful if config/database.php was already set to 'prefix' => env('DB_TABLE_PREFIX') so that one need only change the .env file on first installation

@simmbiote why? That's another call to the env file that probably less then one percent do. Plus that probably should be hard coded in.

I'd suggest that your prefix won't (shouldn't) change between environments. Set a string value in config/database.php and be done with it.

@simmbiote That's just lazy. One extra line...........

@deringer what's the reason for that? Is it a good idea or not in general to use prefixes with laravel? @jekinney is it slower to refer to the env file?

Not nesesary but as your file gets larger yes.

Any case to ensure every deploy or use of your apps code something like table prefix should be hard coded. What if you swap servers and forget. As the env is not in source control, be easy to forget. It's not a security issue as like db login info that's different per server anyways.

Prefix is a constant, never changing once set.

You can make the prefix whatever you want it to be, but it's shouldn't change between instances of your application. Ideally, your application's tables belong in a single database. If you're mixing multiple applications into a single database, I'd advise against that.

How do you prefix in the migration, so your tables gets prefixed accordingly during migration run?

@nomadme do not use dynamic prefix, it is useless. Hardcode them.

@PMALL - That's not helpful; we need a dynamic schema name prefix or some other solution for our database, based on client site.

You don't state why prefix is useless.

We're using Laravel 5.7 and I'm new to Laravel.