3 category tables with same structure, how to manager them with one Controller, Model, and view etc at admin?

Not sure what you mean exactly since you didn't gave much data on what exactly yon need help with, but it looks like what you need is a Polymorphic relationship. Check the docs to see if this is what you wanted.

Thanks for your reply and I have add more info above

Give us a use case on how to manage them.

Like when viewing Business1 you want to manage the business categories only?

and similar posts etc. ?

So do you mean in say one controller one method you want to be able to manage the categories for the associated 'category' being handled?

and also, no that switch is not what you want. or at least I'm not sure why you'd want it. You want to figure out which Model you are working with right?

One thing to remember is that if you have small controllers: BusinessCategoryController.php PostCategoryController.php ...

Then it's really not a big deal to manage the code. It makes it simplier as your rules grow.

Then in the background you could have a Repository class or something that provides the implementation details for any category type regardless of type

Give us an example of what you mean by manage?

ps. yeah, one model will do. I don't know about views. probably at least some with some partials for different aspects.

Firstly, you have a bad database structure :)

As for your issue (caused by a bad database structure) you could create a factory class that returns a model instance based upon the provided table name.

I personally just have a Polymorphic type setup so categories can be shared across models. Still, that may get a little more complicated depending upon how (or if)you store hierarchy data (i.e. parents/children etc.)

Thanks for all of reply and so that I have to code repeatedly for admin at back

categories add, edit

categories2 add, edit

categoriese3 add, edit

... so on.

@martinym I'd personally have a single screen. On the screen I'd have some form of drop down where you can select the associated model.

I certainly wouldn't make 3 controllers or different route resources.

On the relations front you may find https://stackoverflow.com/questions/35100615/using-eloquent-polymorphic-relationships-to-categorise-data-in-laravel helpful.

@Robstar Thanks for your help, now I understood the

each controller corresponds to one table only.

no. it doesn't the controller should JUST process the request and return a response.

ideally you delegate to other classes and methods to do the actual work.