Hi List!
Marc wrote:
Maybe a 2.2.3 before 2.2.4?
Maybe, yes ;)
Do you mean releasing the new version with the new config/http/cookie mecanism?
Nope it was before I add this one. So we may now wait till you have build the session wrapper and then release a 2.3.0-rc1 (isn't it a major change ?)
A 32 MB table dump (uncompressed) still gets a memory limit error on the server.... since with phpMyAdmin 2.1.0 the same table dumps ok.
OK but now you see a php error message where, most of the times, you just faced a "file not found" error before. The "improvement" I wa talking about is just that. To fix the whole problem you described here I'm afraid we have either to remove the *zipping options, either to write temporary files on the server.
[About pointers]
Looks ok with NN 4 and IE 5.5, will try tonight with good old Konq :)
Fine :) BTW I'm not really happy with the style of the left pointer: I don't like the flashy color so much and maybe we should add something to emphasis to db name. Any suggestions?
Loïc
______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif
----- Original Message ----- From: "Loïc" loic-div@ifrance.com To: "phpMyAdmin" phpmyadmin-devel@lists.sourceforge.net Sent: Monday, December 10, 2001 4:37 PM Subject: Re: [Phpmyadmin-devel] 2.2.4 revision
Hi List!
Marc wrote:
Maybe a 2.2.3 before 2.2.4?
Maybe, yes ;)
Do you mean releasing the new version with the new config/http/cookie mecanism?
Nope it was before I add this one. So we may now wait till you have build the session wrapper and then release a 2.3.0-rc1 (isn't it a major change
?)
A 32 MB table dump (uncompressed) still gets a memory limit error on the server.... since with phpMyAdmin 2.1.0 the same table dumps ok.
OK but now you see a php error message where, most of the times, you just faced a "file not found" error before. The "improvement" I wa talking about is just that. To fix the whole problem you described here I'm afraid we have either to remove the *zipping options, either to write temporary files on the
server. How to test if a zipping option is cheked and if not use the old style dump else use the new one. Then almost the uncompressed dump may always works.
[About pointers]
Looks ok with NN 4 and IE 5.5, will try tonight with good old Konq :)
Fine :) BTW I'm not really happy with the style of the left pointer: I
don't
like the flashy color so much and maybe we should add something to emphasis to db name. Any suggestions?
Loïc
____________________________________________________________________________ __
ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
scuse my spelling
Saludos Eduardo Cintas
Eduardo Cintas a écrit :
----- Original Message ----- From: "Loïc" loic-div@ifrance.com
A 32 MB table dump (uncompressed) still gets a memory limit error on the server.... since with phpMyAdmin 2.1.0 the same table dumps ok.
OK but now you see a php error message where, most of the times, you just faced a "file not found" error before. The "improvement" I wa talking about is just that. To fix the whole problem you described here I'm afraid we have either to remove the *zipping options, either to write temporary files on the
server. How to test if a zipping option is cheked and if not use the old style dump else use the new one. Then almost the uncompressed dump may always works.
I like this idea.
Marc
-
Eduardo Cintas -
Loïc -
Marc Delisle