Really depends on what you are trying to achieve. If those tables are part of the core application it's a good a idea to create a model for them. If they are however created via your system then create some class that will handle the interaction with the database. Don't use models in that case.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community