[Phpmyadmin-devel] how to improve dump feature

Robin Johnson robbat2 at fermi.orbis-terrarum.net
Fri Sep 28 07:41:03 CEST 2001

On Fri, 28 Sep 2001, [iso-8859-1] Loïc wrote:
> Hi Steve & list!
> The problem you faced are related to two kinds of
> improvements of the 2.2.0 release :
> 1) the compressing features;
> 2) the output buffering feature.
> There is only one way to lower memory usage IMHO:
> to display dump statements one  by one. It means that
> we should stop output buffering while building dump
> (easy to do) and create a temporary text file on the
> server that will contain the dump statements before to be
> compressed if compression mode is required.
> It means we have to setup a directory that is readable
> and writable by the script where to put these temporary
> files.
That is not an option, as it can create more security holes, and I believe
it will not work in same cases with PHP in safe mode.

Would there possibly be a way, that we can compress the dump statements
one by one as we send them? Possibly an implicit flush when we are using
gzip'd output buffering?

Robin Hugh Johnson
QTOD: "I used to be an idealist, but I got mugged by reality."
E-Mail     : robbat2 at orbis-terrarum.net
ICQ#       : 30269588 or 41961639
Home Page  : http://www.orbis-terrarum.net
Time Zone  : Pacific Daylight (GMT - 8)
geekcode.com ebb.org/ungeek
GCS/M/IT d-(+) s+:- a--- C++++
U++++ L++++ P--(+) W++ K++ PS+
N++ w--- O E---- M-(+) V-- Y++
PE++ PGP++ t-- 5 X+ R tv- b+++
D++ G++ e(*) h! r-- !y+
------END GEEK CODE------
-----PGP INFO-{---
Key ID:0x7E20DFA1
5447C73A 30FB144C 89521B69 2D6A615E 7E20DFA1
---}-PGP INFO-----

More information about the Developers mailing list