Bill Hernandez wrote:
I am running on OS X 10.5.7 on an iMac 24 Intel machine, spend 10-14 hours a day programming, and hardly ever experience any kind of an application hang, much less a crash.
Several days ago I downloaded and installed Zend Server CE, which came with phpMyAdmin.
I have been using Navicat with mySQL and pgSQL for a long time, and for the most part have experienced no problems.
Over the past few days I have tried to move away from Navicat, but phpMyAdmin crashes almost every time I use it.
I have been reading in an sql file that creates some tables, triggers, adds a few records. There's less than 10 records involved and 3 tables.
( 1 ) Select the database ( 2 ) Click on SQL icon ( 3 ) Click on "Import Files" link ( 4 ) Import the file containing the Structure and Data ( 5 ) Try to select a table to view the records
( 6 ) Everything appears fine, but as soon as I try to select a Table to view the records, phpMyAdmin crashes.
I have also tried creating a table from scratch, adding a few records, and exporting the Structure and Data to a file.
How does the crash represent itself to you? White page, back to login screen, or an error message? Anything in the php error log?
Could you attach the sql file on which causes the problem?
I will then drop the database, and create a new one.
At this point I will try steps ( 1 ) through ( 6 ) again with the same results.
It doesn't matter whether I try to import the sql file exported from Navicat, or the one exported from phpMyAdmin. It crashes regardless.
BTW, I have had to go back to Navicat, and it has yet to crash. It does run rock solid, but has problems exporting out of mySQL and importing into pgSQL, so it's not perfect either. I would love to be able to use phpMyAdmin, and with any luck someone will have a clue.
One other thing, when I log into phpMyAdmin, it lets me in the door, but as soon as I select a database, it immediately takes me back to the Login Screen and makes me login again.
Then how do you come across step (1)? ;)
This might very well be a cookie/session problem... Have you looked at the included Documentation.html?