Skip to content
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

SQLSTATE error on migration #2058

Closed
2 tasks done
zmorrow opened this issue May 20, 2016 · 8 comments
Closed
2 tasks done

SQLSTATE error on migration #2058

zmorrow opened this issue May 20, 2016 · 8 comments

Comments

@zmorrow
Copy link

zmorrow commented May 20, 2016

Expected Behavior (or desired behavior if a feature request)

Looking for migration to complete successfully.


Actual Behavior

This is copied from the command line:

Basic usage: composer
For more information just type "composer".

C:\inetpub\wwwroot\snipe-it>php artisan migrate


  • Application In Production!     *
    

    Do you really wish to run this command? (yes/no) [no]:

    yes

    **[Illuminate\Database\QueryException]
    SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'option

    name'; check that column/key exists (SQL: alter table settings drop opti on_name)

    [PDOException]
    SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'option_
    name'; check that column/key exists**_


Please confirm you have done the following before posting your bug report:


Please provide answers to these questions before posting your bug report:

@dmeltzer
Copy link
Contributor

Hi,

Are you using sqlite by any chance?

@zmorrow
Copy link
Author

zmorrow commented May 20, 2016

Hey, no just mysql.

@dmeltzer
Copy link
Contributor

Tracked down the problem. Working on a fix presently. The code that deleted the option_name and option_value previously was commented out when imported to v3, so the migrations run fine on a new database but not one that has been used for 2.*

@zmorrow
Copy link
Author

zmorrow commented May 20, 2016

You da man! Thanks bud!!

@dmeltzer
Copy link
Contributor

If you have the chance to test the commit in PR #2060 and see if it makes your life better, that would be great!

@zmorrow
Copy link
Author

zmorrow commented May 20, 2016

I responded over on #2060 , still not liking it when I un-comment those lines. Thanks for the help!

@snipe
Copy link
Owner

snipe commented Jun 2, 2016

Are you still having this issue wit the latest off v3 branch?

@zmorrow
Copy link
Author

zmorrow commented Jun 2, 2016

Im good, had an issue with importing yesterday but did a fresh pull and all good now. Thanks again you are awesome!

@snipe snipe closed this as completed Jun 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants