Hi List!
So let's go for the 2.2.1-RC1 at the end of this week-end if
everyone agree.
If someone is using Konqueror here I would like him to do
some testings before I commit updates to the cvs tree
(send me a mail please).
>Currently in the army for one last week (working for the
>"Swiss Raid Commando"
I hope you like the rainy day we have today :p
What is your team number? (just to see whether you look like
a winner or a looser today ;))
Good luck Olivier,
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
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.
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
>Why would we _need_ to send the reload headers if
>we are giving the client the download headers?
To bypass the server timeout. But it's not a so good
idea.
And if we want to bypass the server timeout don't we
also have to send nph headers or something like that?
>gzip in that case does indeed work in blocks, and I
>am certain we can exploit that to our advantage.
Yes but what about zip and bz2 (we may skip the
second one of course, but zip is really usefull and
far more widespred than gzip)?
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
>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.
I fully agree.
>Would there possibly be a way, that we can compress the
>dump statements one by one as we send them?
I can't imagine a way to do this:
- you can not send headers to enforce download and
headers to reload the script in the same time;
- you can not compress by parts as far as I know (ie
compress the beginning of the dump, then append
a second compressed part of the dump....).
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
Hi,
i have some trouble with the dump feature.
Have anybody test it with tables greater than 15 MB and
a slow server (350 PII)? It is impossible to get a dump
from big table with the current version, but the 'old'
phpMyAdmin 2.2.0 handle these tables easy.
The previous versions of phpMyAdmin have build the dump
during the client have get. This method save memory and time
because, with the current method the script build first the
complete dump and then send it to the server.
If the PHP settings for memory usage
(--enable-memory-limit,memory_limit <= 8M)
and max time (max_execution_time < 30) to small,
phpMyAdmin _must_ break by small tables with size,
is over 5MB because the php tread have no more resources.
I think we should turn back to the old method.
What you think about it?
--
Steve
Hi,
why we have the follow double strings lang/* files?
tbl_properties.php3 ldi_table.php3
----------------------------------------------------------
$strFieldsEscapedBy = $strFields.' '.$strEscapedBy
$strFieldsEnclosedBy = $strFields.' '.$strEnclosedBy
$strFieldsTerminatedBy = $strFields.' '.$strTerminatedBy
$strLinesTerminatedBy = $strLines.' '.$strTerminatedBy
can we delete one of these strings ?
Regards,
--
Steve
hi list !
Here you can see my last creation of phpMyAdmin logo,
http://www.xmach-fr.org/big_logo.gif
That the big version, when you see the small version it must beautiful :)
What you think, is important !
Michael-_
Geert the cookie "security issue" is fixed in the cvs tree.
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