-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
allow us to configure the table on different connection / database please #84
Comments
Oh.. right.. it's working because the |
Hi @vesper8! So we don't need to do anything at this moment? |
Erm.. sorry if my reply was misleading, I was only explaining why the The |
I understand. Unfortunately, I don't have enough time for this at the moment. I spend weekends on https://hype.me improvement and a new secret (🙊) open source application. @vesper8 I'm ready to review this feature, if you want to bring it in the same way as it done in Laravel Love. |
Hello!
As you know me from my heavy usage of your awesome laravel-love library, I like to split my laravel projects into many databases and I'm doing this for one that uses your laravel-ban package.
My
bans
table is on a different database then my main one. Oddly, methods such asisBanned()
do not return any error. To be clear, my bans table is on a different database and theisBanned
does correctly return true or false.. so it somehow is capable of interacting with the bans table on a different connection. How this is working right now is a bit puzzling!!But when I try to actually
->ban()
someone I get an error because it's looking for thebans
table on the wrong connection.Would it be possible for you to add a configuration to allow us to set a different connection please?
The same way you did it on
laravel-love
would be perfect:Many many thanks!
The text was updated successfully, but these errors were encountered: