-
Notifications
You must be signed in to change notification settings - Fork 84
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
Prefix db (table not found) #131
Comments
@mgralikowski, I will check the repository code to make sure it uses the variable for the translation table instead of assuming that it is |
I found Your method adjustTranslationTable(). For me is not proper way (better is variable with prefixed table name or with only prefix) but do a job ;) My PR remove space which cause that replacing doesn't work. |
@mgralikowski, in repository the proper function is I missed a whole bunch of queries which used I am fixing it now and will release a fixed version. |
@mgralikowski, fixed version released. |
Should i use master version to get this fix? For now i use 5.5. |
@mgralikowski, I will need to apply the fix to 2.5 branch. |
Is master branch safe to use in production and L 5.5? |
@mgralikowski, I have not tested it with 5.5 and there were a lot of changes in that branch from laravel 5.5 branch. Unless you upgrade to Laravel 5.6 I would not recommend it. |
Ah, ok. So please, just accept pull request with this small fix #132 in 5.5 branch. It's enough for me to make production deployment. |
@mgralikowski, made a release into Laravel-5.5 branch with merge #132 |
There is a problem with database prefixing.
Library ignores that default connection has set "prefix".
Furthermore if i try to manually change column to "ltm_translations" (to non-prefixed version) still is error, this time:
I guess there is mix of raw queries and eloquent queries. The solution is use DB::getTablePrefix() or similar in this raw queries.
The text was updated successfully, but these errors were encountered: