Crash on content display after column addition.

[GoogleCodeExporter]

What steps will reproduce the problem?

Looked at a table in content view.  Ordered by ID desc (clicked the id column 
so that the order would be desc).  Table has about 200K rows in it.  Then 
clicked the structure icon, and added in a new DATETIME column (although any 
column creation causes this).  Clicked back on the content view.  Crash after a 
while of the spinning beach ball. 

What is the expected output?
Not a crash.  Expected to see updated column added to the content pane.

What do you see instead?
Spinning beach ball then crash.

What version of Sequel Pro are you using?
1.02

What version of OS X are you using?
10.7.5

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

Original issue reported on code.google.com by varc...@gmail.com on 11 Sep 2013 at 7:41

[GoogleCodeExporter]

Hi varchar,

We've had similar reports a number of times, although I've never been able to 
reliably reproduce it :(

However, we have just rewritten a lot of the data storage handling, and I was 
thinking about this problem while doing it.  If you can reliably reproduce this 
(preferably against a test database...) I'd love it if you could test a nightly 
and let me know if the problem still persists?

We make nightlies available at http://nightly.sequelpro.com , and if you could 
give the latest one a spin, that'd be great.  Because these aren't tested as 
widely as the releases, we don't recommend their use against production data, 
just in case...

The table storage rewrite should result in faster table loads and lower memory 
use for loaded data, and it'd be great to know if it also addressed this or if 
there's still problems with some environments...

Original comment by rowanb@gmail.com on 11 Sep 2013 at 10:07

• Changed state: WaitingOnUser

[GoogleCodeExporter]

Closing after no further feedback.

Original comment by stuart02 on 21 Oct 2013 at 6:11

• Changed state: WontFix