-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Illuminate\Database\QueryException #9755
Comments
Laravel 4.2 is not supported, sorry. |
It would be nice to have at least a useful hint like "upgrade to the latest framework". A "We are not helping" response is pretty lame. |
FYI, if anybody else has an older version of the framwork and gets an issue: Add in
After having done that you get a proper error message and can start debugging. |
// try this Way increments('id'); $table->integer('role_id')->unsigned(); $table->string('name'); $table->string('email',50)->unique(); $table->string('username'); $table->string('password'); $table->boolean('active'); $table->rememberToken(); $table->timestamps(); }); } public function down() { Schema::dropIfExists('users'); } } |
this is a very old issue that was closed nearly 6 years ago, i don't think it's usefull to comment here |
Zo'r gap yo'q malades bosing endi |
Preconditions
I am packaging an app called Paperwork which has been created with the Laravel Framework for a platform called Sandstorm. I first have build the package with Docker and now switched to Vagrant for that. I have a problem migrating old instances of the package which have been created with Docker to the new version.
Issue related to the Laravel Framework
At one point an error from the Laravel Framework is shown which indicates an issue with the MySQL connection or the database elsewhere but instead of showing a helpful SQL error a "Class not found" error is shown.
How to reproduce the issue
Take an existing app with database and rename a random used table to something else.
Expected behavior
The raised error should show a message like "table xyz not found" or something else helpful should be shown, like "advertised" in the code:
Current behavior
The following message appears which doesn't help to track down the root cause:
I guess that the class
QueryException
is a component of the Laravel Framework which has been changed or doesn't work as expected.Can you please help me with that? Am I guessing right or is the cause of the not so good fatal error exception not based in the Laravel Framework?
FYI: a screen shot of the error message:
The text was updated successfully, but these errors were encountered: