December 2003 - Developers - lists.phpmyadmin.net

[Phpmyadmin-devel] phpMyAdmin 2.5.5-rc1 is released
by Marc Delisle 07 Dec '03

07 Dec '03

The Internet, 2003-12-07 Greetings, The phpMyAdmin development team is pleased to announce the availability of the first release candidate for phpMyAdmin 2.5.5. About 2.5.5-rc1 --------------- New minimum version requirements: phpMyAdmin now requires at least PHP 4.2.x and MySQL 3.23.36. MySQL 4.1 Note: phpMyAdmin's MySQL 4.1 support is still experimental Improvements: * General code optimization by removing old PHP3-compatibility * Make default functions configurable * Visual scratchboard: show column names * Show overhead in table list, allow to check all overheaded tables at once * Export: can suppress dates information * MySQL error messages improved formatting * Printview: display linked values and other relational features * Export: allow delayed INSERTs, and support for UPDATE and REPLACE statements * Show result of last SHOW query when using multiple queries * Can now specify the default query * Catch table renaming with dot in the new name * Multi-row edit * Date MIME transformation: show also real data before transformation Fixes: * Relation view: non-unique keys were not displayed as possible choices for foreign keys * Try to upload history in table only if configured so * Opera and Export dynamic options * Try to show sorting by indexes only if makes sense * Some undefined variables * SQL-history and js errors * Export and CSV for Excel can now choose the Excel edition * Multi-row delete in vertical mode * Execute stored bookmarks had a problem * Transformations: now allow more timestamps * Export: added XML header * Could not enter the string "NULL" * Export: fixed LaTeX output, and unique fields are now bold * Export: foreign keys problem * FULLTEXT is possible not just on TEXT but also MEDIUMTEXT, etc * Now we can kill more processes * Display problem with repeated headers * In Server view, left frame did not keep server choice, language, etc * Sort on some aliased columns did not work Download/support information on http://www.phpmyadmin.net. Marc Delisle, for the team.

1 0

[Phpmyadmin-devel] Pause from phpMyAdmin
by Michal Cihar 05 Dec '03

05 Dec '03

Hi all due to finishing school I won't have much time for phpMyAdmin in next about three months. Only thing I will probably do is keeping Czech translation up to date. I'll keep items in feature requests assigned to me, but if anyone of you will want to write that feel free to reassign them. -- Regards Michal Cihar http://cihar.com

4 4

[Phpmyadmin-devel] On Documentation.txt
by Alexander M. Turek 05 Dec '03

05 Dec '03

Hi list, It's just a thought, but couldn't the Documentation.txt file be created by create_release.sh automatically when building a distribution kit? I can't see the point of having this file inside the CVS tree since it contains redundant information. Regards, -- Alexander M. Turek <rabus(a)users.sourceforge.net> _ __ __ _ _ _ _ __ | |__ _ __ | \/ |_ _ / \ __| |_ __ ___ (_)_ __ | '_ \| '_ \| '_ \| |\/| | | | | / _ \ / _` | '_ ` _ \| | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|\__, /_/ \_\__,_|_| |_| |_|_|_| |_| |_| |_| |___/ <http://www.phpmyadmin.net>

4 8

[Phpmyadmin-devel] require_once
by Michal Cihar 04 Dec '03

04 Dec '03

Hi all As we dropped PHP 3 support, we might also want to start use require_once to get rid of bug #571409. Does any of you know something that will need special care or just replacing every require with require_once should be okay? -- Regards Michal Cihar http://cihar.com

4 5

[Phpmyadmin-devel] 2.5.5-dev and browser transformations
by Marc Delisle 04 Dec '03

04 Dec '03

Hi, is it just me, or we have lost since the last few changes, the value of Browser transformations? MIME-type and transformation options are still there in the structure page of my field, but Browser transformation is blank. Marc

2 2

[Phpmyadmin-devel] demo problem (preg_match)
by Marc Delisle 04 Dec '03

04 Dec '03

Hi, can someone have a look at the demo problem: Warning: Compilation failed: missing terminating ] for character class at offset 13 in /home/groups/p/ph/phpmyadmin/htdocs/phpMyAdmin/libraries/common.lib.php on line 1108 This does not happen on my server. Marc

3 2

[Phpmyadmin-devel] [phpMyAdmin translation] Feedback
by FrostyRain20034＠aol.com 04 Dec '03

04 Dec '03

Before you contact our translator, please note: - Each language file is included in this distribution. The translator won't send you any translations. - There are no localized documentations yet. - The translator won't provide any type of e-mail support. If you have any questions about configuring or using phpMyAdmin, please use our support forum or the users email list. ------------------------------------------------------- Dear translator: just ignore this mail. I haven't read the text above and just submitted the mail as my client displayed it...

1 0

[Phpmyadmin-devel] Re: PHP 3 Compatibility
by Michal Cihar 04 Dec '03

04 Dec '03

Hi all moving this duscussion to list, because I thing it should be there :-) Original message (Garvin Hicking, 19.11.2003 11:57): > a) Wait until after 2.5.5 RC1 and apply changes to HEAD then. > Pro: No hurry for now. > Con: I might not have the time then :) No need to wait, if you have time :) > b) Branch off a QA_2_5_5 tree now, make the RC out from that branch > and apply my changes to HEAD now. > Pro: Work can start immediately, a quite stable 2.5.5 release. > Con: Later PHP4-enabled release We will say that we don't support php3, but the code will still contain many things for php3... > c) Branch of a PHP4_QA tree, apply my changes to that branch, merge > the changes to HEAD later on. > Pro: Agitate on a 'secure' branch, work can start immediately > Con: Maybe harder to merge afterwards, less people testing it (because > CVS snapshot is from HEAD, and people using CVS directly will most > likely use HEAD as well). People expect HEAD to be the currently developped one, changing this confuses them. > d) Make changes to HEAD. Make 2.5.5 the first PHP4-release, thus > moving the 2.5.5 RC1 about 1-2 weeks later and having huge changes in > that 2.5.5 release. > Pro: Making a real worthy 2.5.5 release? Work can start immediately. > Larger testing user base. > Con: No 2.5.5 release with the latest features, moved schedule. Good solution. If there are not any things that are worth of releasing quickly, I'd prefer this. -- Regards Michal Cihar http://cihar.com

4 5