-
Notifications
You must be signed in to change notification settings - Fork 20
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
Laravel 4.2 #2
Comments
@jorisnoo, I'm currently working on this but having some problems. |
This package its so helpful, it would be great if you manage to update it, thanks a lot. |
Any thoughts as to where in the Laravel workflow you set the schema name. I ask because while I am able to switch between databases at run time using a 'before' filter, this does not seem to work for schema (i.e. the change in schema name seems to happen after the database objects have been instantiated and point to the original schema name). Cheers. |
Controller? |
@pspiteri you shouldn't have problems using a filter like this to change between schemas https://github.com/pacuna/laravel-multitenancy-schemas/blob/master/app/routes.php is that what your trying yo accomplish? |
Thanks @pacuna - yes, that is it. Yeah ... this didn't work for me. But I have compare your code to mine and that is pretty close to being the same. So I did some more research and added this line right at the end of the filter ... DB::setDefaultConnection('tenant'); ... and what do you know - it works. I have two pgsql connections setup - one tenant (which I change the schema on) and one public, or shared - and I have set my default connection as the 'public', so perhaps this is why I required this line. Thanks you very much for getting back to me - it has been very useful to have something to compare to. |
closed since now support for Laravel 5 has been added. |
Hi, I'd love to try this package.
It currently lists "illuminate/support": "4.1.x" as dependency, which makes it incompatible to the newest version of Laravel. Could you consider updating it to 4.2.x?
Thanks!
The text was updated successfully, but these errors were encountered: