Very slow interface when query history is very large

[Tom H]

Ok, so here's a fun little story. I happened to copy a VERY large query statement (basically the contents of a ~500mb .sql file) into the query tab and executed it. after this happened, sequel pro became extremely slow, taking a minute or so to react to any interactions with it. it took me a while to figure out what was going on, but after poking around, i happened to notice that it's plist file had ballooned to 1.3gb. i figured it was keeping that very large query statement in history somewhere, and after several minutes of waiting for sequel pro to respond, i was able to get to the query tab again and clear the global query history. things went back to normal after this. 

anyway, i realize that doing things like copy/pasting extremely large statements into sequel pro is not a good idea, but i thought i'd pass along this anecdote, in case it might lead to some way of helping sequel pro defend itself against very dumb user actions such as these. 

cheers,

-Tom

[Rowan Beentje]

Hi Tom,

You're absolutely right - this is an issue, especially for users who don't realise what's happening after running several big queries...

http://spbug.com/687 is tracking this issue at the moment; to address this we'll have to move some history to a file, or use gzip, or something similar.

(There's always File > Import for huge SQL; I can't imagine 500MB in the editor would be very pleasant either!)

Rowan

> --
> You received this message because you are subscribed to the Google Groups "Sequel Pro" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/sequel-pro/-/hsFkTmLmWZMJ.
> To post to this group, send email to seque...@googlegroups.com.
> To unsubscribe from this group, send email to sequel-pro+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sequel-pro?hl=en.