Dave Page wrote:
The longer you use it, the longer it takes to connect to databases each time you start up. It says "Restoring previous settings".
It should only take longer if the number of objects in your database grows significantly, or if you've turned on debug logging. At that point it is examining your database so that it can rebuild the treeview to roughly the state that it was when you last used it.
My database has 270+ tables. That's probably small for where it will be in a year. At the moment I have only a dozen or so databases per server, and four servers that I regularly connect to. I did not intentionally turn on debug logging.
I am considering making that behaviour optional though - I have many databases for instance, and often find myself wating a few seconds needlessly.
Yeah, it's hard to complain about seconds, but delays of that sort do upset concentration. The problem is compounded when I have to kill it and restart it for a network hang.
On my linux box, it also has the dubious honor of being the only program I have ever seen that can lock X hard, with killing the X server being the only rescue (if you call that a rescue). It can connect over networks, but on mine it always seems to hang after an hour or so, and you have to kill it and restart it.
That's a new one. Any other symptoms? Can you get a backtrace from a coredump?
I'll answer this in another email, I'm about to deliberately freeze my X server and won't be able to answer :)
Finally, it ain't great for inspecting text columns.
How so- the in-grid editor? I'm open to suggestions and feedback.
The results display in the query analyzer shows one results at one row height. If a text column has CR's in it, such as the text of a stored procedure, or a stored XML file, you can't see anything. There appears no way to increase the height of the displayed result, so all I see is the first line. Ideal would be a display that sized itself to the height of the content. Then I'd be clean out of phppgadmin.
phppgadmin has the edge here because they simply dump the result to the display and the browser sizes it.
Regards, Dave.