Hi,
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
Marc
Hi Marc
On 19.04.2004 14:17 -0400, Marc Delisle wrote:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
Login cookie validity induced logouts too soon
This happened only in cvs, you should mention https://sourceforge.net/tracker/index.php?func=detail&aid=902295&gro... instead of that...
Michal Čihař a écrit:
Hi Marc
On 19.04.2004 14:17 -0400, Marc Delisle wrote:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
Login cookie validity induced logouts too soon
This happened only in cvs, you should mention https://sourceforge.net/tracker/index.php?func=detail&aid=902295&gro... instead of that...
Michal,
Thanks I will do the modifications.
Marc
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
I think the charset improvements should be more obvious. But otherwise - very nice. Thanks!
Marcel
Marcel Tschopp a écrit:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
I think the charset improvements should be more obvious. But otherwise - very nice. Thanks!
Marcel
Like this?
Improvements:
* mysqli extension support - direct support for MySQL 4.1 charsets -------
I was wondering if we could list the other benefits of mysqli. Any volunteers?
Marc
On Mon, 19 Apr 2004 14:37:26 -0400 Marc Delisle wrote:
Marcel Tschopp a écrit:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
I think the charset improvements should be more obvious. But otherwise - very nice. Thanks!
Marcel
Like this?
Improvements:
* mysqli extension support - direct support for MySQL 4.1 charsets
Yeah! I think it's one of the biggest improvements in PMA 2.6.0...
I was wondering if we could list the other benefits of mysqli. Any volunteers?
Hmm... better PHP5 support? Better memory management?
Marcel
On 19.04.2004 20:42 +0200, Marcel Tschopp wrote:
On Mon, 19 Apr 2004 14:37:26 -0400 Marc Delisle wrote:
I was wondering if we could list the other benefits of mysqli. Any volunteers?
Hmm... better PHP5 support? Better memory management?
http://www.zend.com/php5/articles/php5-mysqli.php
Especially "Major Features" there...
Marcel Tschopp a écrit:
On Mon, 19 Apr 2004 14:37:26 -0400 Marc Delisle wrote:
Marcel Tschopp a écrit:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
I think the charset improvements should be more obvious. But otherwise - very nice. Thanks!
Marcel
Like this?
Improvements:
* mysqli extension support - direct support for MySQL 4.1 charsetsYeah! I think it's one of the biggest improvements in PMA 2.6.0...
I was wondering if we could list the other benefits of mysqli. Any volunteers?
Hmm... better PHP5 support? Better memory management?
Marcel
I updated the release notes.
SourceForge is back now, but I will wait to tomorrow, after latest Alexander's review, and possibly more feedback on the release notes.
Marc
Hi Marc & list,
Marc Delisle wrote:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
imho, we can remove that note about the MySQL 4.1 / 5.0 support being experimental. I was about to remove those notes from our Documentation, but I wanted to ask you first.
"MySQLi: direct support for MySQL 4.1 character sets" does not make much sense as we also have this direct charset support with the classic extension.
The thing about MySQLi is that it was designed for the use with MySQL 4.1 while the classic extension officially does not work with MySQL 4.1... Actually, it does still work fine with MySQL 4.1, but its programmers don't seem to trust their baby anymore... ;-)
I'd like to change "ANSI compatibility" into "Optional ANSI compatibility" as the user does not have to stick with ANSI-SQL if he does not want to.
The popup calendar is not only available for date fields but also for datetime and timestamp afaik.
I'd move "UTF-8 was disabled on UTF-8 databases" under "Improvements" and call it "Support for UTF-8 databases under MySQL 4.1"
"MySQL charsets not added to WHERE clauses": Perhaps we should mention that this problem occured with the search feature.
Fixes: Charset information got lost when changing fields, see ChangeLog 2004-04-17.
Improvements: "(Un)check all" link for privileges page, see ChangeLog 2004-04-03.
Could someone explain "Export: use unbuffered queries" to me?
Regards,
Hi again,
Alexander M. Turek wrote:
"MySQL charsets not added to WHERE clauses": Perhaps we should mention that this problem occured with the search feature.
Forget about what I wrote; Of course the bug was not only related to the search script.
Regards,
On 19.04.2004 23:19 +0200, Alexander M. Turek wrote:
I'd like to change "ANSI compatibility" into "Optional ANSI compatibility" as the user does not have to stick with ANSI-SQL if he does not want to.
It's not optional (you can not enable/disable it), better to say partial - it changed comments and quoting, but MySQL specific stuff in CREATE TABLE are still there.
The popup calendar is not only available for date fields but also for datetime and timestamp afaik.
Exactly.
Could someone explain "Export: use unbuffered queries" to me?
Query result is not read as whole by php, but passed record by record to script, see http://php.net/mysql_unbuffered_query and http://php.net/mysqli_query with MYSQLI_USE_RESULT.
Hi all, updated version:
http://www.phpmyadmin.net/home_page/marc.php?rel=0
Waiting a few hours for alpha release.
Marc
Alexander M. Turek a écrit:
Hi Marc & list,
Marc Delisle wrote:
Please have a look at http://www.phpmyadmin.net/home_page/marc.php?rel=0
and send me your additions/corrections.
imho, we can remove that note about the MySQL 4.1 / 5.0 support being experimental. I was about to remove those notes from our Documentation, but I wanted to ask you first.
"MySQLi: direct support for MySQL 4.1 character sets" does not make much sense as we also have this direct charset support with the classic extension.
The thing about MySQLi is that it was designed for the use with MySQL 4.1 while the classic extension officially does not work with MySQL 4.1... Actually, it does still work fine with MySQL 4.1, but its programmers don't seem to trust their baby anymore... ;-)
I'd like to change "ANSI compatibility" into "Optional ANSI compatibility" as the user does not have to stick with ANSI-SQL if he does not want to.
The popup calendar is not only available for date fields but also for datetime and timestamp afaik.
I'd move "UTF-8 was disabled on UTF-8 databases" under "Improvements" and call it "Support for UTF-8 databases under MySQL 4.1"
"MySQL charsets not added to WHERE clauses": Perhaps we should mention that this problem occured with the search feature.
Fixes: Charset information got lost when changing fields, see ChangeLog 2004-04-17.
Improvements: "(Un)check all" link for privileges page, see ChangeLog 2004-04-03.
Could someone explain "Export: use unbuffered queries" to me?
Regards,
Hi there,
Marc Delisle wrote:
Hi all, updated version:
Looks good. Although we do not plan to release a second alpha, I'd suggest to name this one "2.6.0-alpha1", just because we do so for release candidates and patch levels, too.
Waiting a few hours for alpha release.
I'm done with everything, so you can release if you want. If the offset error is hard to fix at the moment, just leave it for now: I don't think that it would be a showstopper for an alpha release.
I prepared a release announcement for the alpha release because I thought it could be helpful for attracting testers... You'd just need to add your list of changes. :-)
As you might notice, I modified the copyright line inside the announcement: I only listed those developers that actually worked on this release. Since we are still referring to the credits sections of the docs, this should be OK, as far as I can tell. I'd like to use this one in our README, too, if you don't have any objections.
Let's have a clean 2.6.0.
Alexander M. Turek a écrit:
Hi there,
Marc Delisle wrote:
Hi all, updated version:
Looks good. Although we do not plan to release a second alpha, I'd suggest to name this one "2.6.0-alpha1", just because we do so for release candidates and patch levels, too.
Waiting a few hours for alpha release.
I'm done with everything, so you can release if you want. If the offset error is hard to fix at the moment, just leave it for now: I don't think that it would be a showstopper for an alpha release.
I prepared a release announcement for the alpha release because I thought it could be helpful for attracting testers... You'd just need to add your list of changes. :-)
As you might notice, I modified the copyright line inside the announcement: I only listed those developers that actually worked on this release. Since we are still referring to the credits sections of the docs, this should be OK, as far as I can tell. I'd like to use this one in our README, too, if you don't have any objections.
Ok for me to change the README. Sorry I released alpha1 before noticing this. Can you change it for the next release?
Also I forgot about the donations section in the message to -devel and -users, but added it for -news.
Marc
-
Alexander M. Turek -
Marc Delisle -
Marcel Tschopp -
Michal Čihař