-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom table names #1063
Comments
No plans for this. |
@driesvints what a "great" response... no explanation, just shutdown. thanks ;) |
You can already overwrite the current migrations if you want: https://laravel.com/docs/8.x/billing#database-migrations But changing the table names will conflict with the existing Eloquent models. That makes it hard to introduce custom table names. In general we don't want to support this because most use cases don't need custom table support and introducing this for a small minority just brings on an unnecessary maintenance burdon on us. |
What about a configurable Subscription model? You already support a custom billable model. If I can set my own Subscription model in the configuration, then I'm able to make a new Subscription model that extends yours and set a new table name directly in it. Then I just overwrite your migrations and I'm done. |
Well actually, adding model swapping in the same fashion as Passport & Sanctum isn't a bad idea at all. I've just sent in a PR to do just that: #1067 |
Great. That was fast. Thanks. Have a great day :) |
No worries. Sorry if I was a bit terse at first. Thanks for bringing this up 👍 |
Table names should be configurable so we can prefix them or just use custom names
The text was updated successfully, but these errors were encountered: