Crash/Hang on refreshing table after alter table command

[GoogleCodeExporter]

What steps will reproduce the problem?
1. View a table of data
2. Run alter table SQL in the query window to add a new column (I used an ENUM 
field)
3. Refresh the table of data

What is the expected output?
The table data is refreshed with the new column in the view

What do you see instead?
The window hangs forever

What version of Sequel Pro are you using?
1.0.2

What version of OS X are you using?
10.8.3

What version of MySQL are you connecting to on the server?
5.3

Original issue reported on code.google.com by madru...@gmail.com on 9 May 2013 at 11:00

[GoogleCodeExporter]

Hi madrussa,

Was this quite a large table?  If so, I think it's the same as Issue #1710...

Original comment by rowanb@gmail.com on 9 May 2013 at 6:28

• Changed state: WaitingOnUser

[GoogleCodeExporter]

It only had about 200 rows in the table so pretty tiny. No changes were made to 
any keys either.

Original comment by madru...@gmail.com on 9 May 2013 at 8:23

[GoogleCodeExporter]

In Sequel Pro 1.0.2 4096 when I have a database connected and on the content 
view, if I modify the table schema through a different interface, in my case 
I'm using RedBeanPHP and adding a field to my table, well when I switch back to 
Sequel Pro and refresh it hangs and then needs killed. So it looks like 
reloading the content view can't handle changes to the table schema when it was 
not done by Sequel Pro itself.

Anyone using RedBeanPHP will likely encounter this hang a lot because it is 
constantly modifying the schema as you are building your application.

Original comment by indieki...@gmail.com on 6 Nov 2013 at 2:46