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

Blob column causes import to fail and hangs sequel pro repeatedly #3216

Open
markl181 opened this Issue Oct 8, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@markl181

markl181 commented Oct 8, 2018

I have a (fairly small) sql file that was exported from Sequel Pro a couple of months ago. I'm setting up a new machine and trying to re-import the same file back into Sequel Pro. When the import ran, I got an error and it failed at the table that contains a mediumblob column. When I attempt to open that table in the UI, Sequel Pro hangs (becomes unresponsive and has to be force quit). When I attempt to drop that table either from the UI or via query, Sequel Pro hangs. The same thing happens if I try to drop the database or any other table (although I can view the other tables). Please let me know how I can fix this.

I'm not sure if it's a bug or not (except perhaps if a corrupt table due to the import is causing all this).

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx Oct 11, 2018

Member
  1. Try this build: https://sequelpro.com/builds/Sequel-Pro-Build-3477d22387.zip
  2. If it still happens, open Activity Monitor, select "Sequel Pro (not responding)", go to View > Sample Process and post the results
Member

dmoagx commented Oct 11, 2018

  1. Try this build: https://sequelpro.com/builds/Sequel-Pro-Build-3477d22387.zip
  2. If it still happens, open Activity Monitor, select "Sequel Pro (not responding)", go to View > Sample Process and post the results
@markl181

This comment has been minimized.

Show comment
Hide comment
@markl181

markl181 Oct 14, 2018

Thanks for your response - unfortunately I needed to get this done so I had to resort to the command line. If it helps at all, I manually dropped each table from the command line and then reimported each table using the create table and insert statements from the sql export file. The fact that this worked suggests to me that there is some type of issue here. If I get a chance I’ll rerun the import to get the error again.

markl181 commented Oct 14, 2018

Thanks for your response - unfortunately I needed to get this done so I had to resort to the command line. If it helps at all, I manually dropped each table from the command line and then reimported each table using the create table and insert statements from the sql export file. The fact that this worked suggests to me that there is some type of issue here. If I get a chance I’ll rerun the import to get the error again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment