2 Feb
2003
2 Feb
'03
9:44 p.m.
The Internet, 2003-02-02
To: phpMyAdmin community
The development team is pleased to announce version 2.4.0-rc1
(first release candidate) of phpMyAdmin.
Improvements:
* PDF pages
o new data dictionary
o support for deleting a PDF page definition
o better browser support
* cookie login: login error message
* new server/user management interface with sub-pages
o more intuitive interface
o support new MySQL 4 privileges
o support for user resource limits
* Export
o export to LaTeX format
o better handling of charset conversion
o better output order of inserts/creates
o export results of any single-table SELECT
* option to only copy data (append) to a table
* better handling of confirmation requests (bookmarks) and LIMIT
* support EXTRACT ... FROM
* check/uncheck all for field selection
* moving cursor with ctrl/arrows in table creation and row editing
* images in PNG format where possible
* display UPDATE SQL statement after a row edit
* in Select sub-page, drop-down for ENUMs
* (experimental) support for compressed connections to the MySQL server
* upload of binary file into a field
* new documentation layout
* (for phpMyAdmin developers) interface to DBG extension for
debugging/profiling
Fixes:
* output handler warning for PHP >=4.3.0
* usernames with "@" character
* links or submit buttons for db search results
* warning for bzip problem of PHP 4.2.1
* wrong "Back" links
* UNION processing generated undefined variables
* handling of "LOCAL" in recent MySQL versions for LOAD DATA INFILE
* wrong drop-down for foreign keys in Select sub-page
* wrong charset information in XML exports
* parsing error for the single quote case
* problem with SQL validator interface
* wrong parsing of INTERVAL and AUTO_INCREMENT
* no longer allow invalid options like UNSIGNED in SET/ENUM
* problem entering comments in Relation view
* fix for kanji encoding problem
* empty field names on add fields page caused problems
Download links, as usual, on http://www.phpmyadmin.net
Marc Delisle, for the team.
2 Feb
2 Feb
10:46 p.m.
On Sun, Feb 02, 2003 at 09:44:03PM -0500, Marc Delisle wrote:
Improvements:
Fixes:
Could everybody please go and close off all the completed
bugs/features/patches/etc. that are assigned to them?
--
Robin Hugh Johnson
E-Mail : robbat2(a)orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
3 Feb
3 Feb
6:52 a.m.
Robin Johnson wrote:
On Sun, Feb 02, 2003 at 09:44:03PM -0500, Marc Delisle
wrote:
Yes, and if someone is not working or planning to work on something
assigned to him, I think it would be better to deassign.
Marc
Improvements:
Fixes:
Could everybody please go and close off all the completed
bugs/features/patches/etc. that are assigned to them?
7:47 a.m.
On Mon, Feb 03, 2003 at 06:47:19AM -0500, Marc Delisle wrote:
*looks at the stuff
assigned to him*
phpMyAdmin - Bugs
647705 (2.3.3) "no" as table alias
678162 (2.4.0-dev) Parser and umlauts
678289 (2.4.0-dev) parser bugreport bug :o)
596692 (2.3.1-dev) SQL pretty printer bugs
564793 (2.2.6) Plain password in Cookie Mode on phpinfo()
474575 (2.2.0) SELECTing a table if no priv for a column
593598 (2.3.0) Parser should use character sets for
phpMyAdmin - Feature Requests
479640 create user and database for an ISP
486080 (DB-Config) Configuration files via the web
485311 (DB-Config) Storing Server Configuration in Database
622553 (DESIGN) SQL Parser reworking
Ok, i'm dropping some of those that never got anywhere
namely #564793, #474575, #486080, #479640
So somebody else can work on them...
DB-Config #485311 is making slow progress, should mature by summer...
(Actually, this is the reason the DBG extension got added, because I put
it in to work on DB-Config...)
--
Robin Hugh Johnson
E-Mail : robbat2(a)orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Could everybody
please go and close off all the completed
bugs/features/patches/etc. that are assigned to them?
Yes, and if someone is not
working or planning to work on something
assigned to him, I think it would be better to deassign.
4:33 a.m.
New subject: [Phpmyadmin-devel] [Phpmyadmin-news] phpMyAdmin 2.4.0-rc1 is released
The Internet, 2003-02-02
To: phpMyAdmin community
The development team is pleased to announce version 2.4.0-rc1
(first release candidate) of phpMyAdmin.
Improvements:
* PDF pages
o new data dictionary
o support for deleting a PDF page definition
o better browser support
* cookie login: login error message
* new server/user management interface with sub-pages
o more intuitive interface
o support new MySQL 4 privileges
o support for user resource limits
* Export
o export to LaTeX format
o better handling of charset conversion
o better output order of inserts/creates
o export results of any single-table SELECT
* option to only copy data (append) to a table
* better handling of confirmation requests (bookmarks) and LIMIT
* support EXTRACT ... FROM
* check/uncheck all for field selection
* moving cursor with ctrl/arrows in table creation and row editing
* images in PNG format where possible
* display UPDATE SQL statement after a row edit
* in Select sub-page, drop-down for ENUMs
* (experimental) support for compressed connections to the MySQL server
* upload of binary file into a field
* new documentation layout
* (for phpMyAdmin developers) interface to DBG extension for
debugging/profiling
Fixes:
* output handler warning for PHP >=4.3.0
* usernames with "@" character
* links or submit buttons for db search results
* warning for bzip problem of PHP 4.2.1
* wrong "Back" links
* UNION processing generated undefined variables
* handling of "LOCAL" in recent MySQL versions for LOAD DATA INFILE
* wrong drop-down for foreign keys in Select sub-page
* wrong charset information in XML exports
* parsing error for the single quote case
* problem with SQL validator interface
* wrong parsing of INTERVAL and AUTO_INCREMENT
* no longer allow invalid options like UNSIGNED in SET/ENUM
* problem entering comments in Relation view
* fix for kanji encoding problem
* empty field names on add fields page caused problems
Download links, as usual, on http://www.phpmyadmin.net
Marc Delisle, for the team.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Phpmyadmin-news mailing list
Phpmyadmin-news(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-news
4:52 p.m.
Hi
On Monday 03 February 2003 03:44, Marc Delisle wrote:
* upload of binary file into a field
JFYI: with binary files it just crashed my browser, now it should really work
;-)
--
Regards
Michal Cihar
nijel at users dot sourceforge dot net
http://cihar.liten.cz
5:01 p.m.
Michal Cihar wrote:
Hi
On Monday 03 February 2003 03:44, Marc Delisle wrote:
Michal,
which browser and which kind of files? I had made tests with .jpg files,
browser IE 6 and Mozilla 1.2.1. No crash at all.
And how users are supposed to know when to click "binary" ?
Marc
* upload of binary file into a field
JFYI: with binary files it just crashed my browser, now it should really work
;-)
4 Feb
4 Feb
2:36 p.m.
Hi
On Monday 03 February 2003 23:00, Marc Delisle wrote:
which browser and which kind of files? I had made
tests with .jpg files,
browser IE 6 and Mozilla 1.2.1. No crash at all.
I uploaded small png and it got displayed in SQL and my mozilla 1.2.1
crashed. Konqueror displayed it, but it was nothing nice.
And how users are supposed to know when to click
"binary" ?
Currently probably every time ;-). I'm going to add documentation about it, I
just didn't have time to write it yesterday. The other possibility is use
only the way that is now used when checked binary, because upload is
currently only for binary fields...
--
Regards
Michal Cihar
nijel at users dot sourceforge dot net
http://cihar.liten.cz
2:52 p.m.
Michal Cihar wrote:
Hi
On Monday 03 February 2003 23:00, Marc Delisle wrote:
Michal,
how do you display the row? I have an application that reads the row in
MySQL,
sends the proper header
and there are no crashes. But maybe this is because of the character
sets when storing
in MySQL.
If we don't have choice, I agree about the encoding you added but we
have to document
this somewhere: users will have to know how to decode it in their
applications.
which browser and which kind of files? I had made
tests with .jpg files,
browser IE 6 and Mozilla 1.2.1. No crash at all.
I uploaded small png and it got displayed in SQL and my mozilla 1.2.1
crashed. Konqueror displayed it, but it was nothing nice.
And how users are supposed to know when to click
"binary" ?
Currently probably every time ;-). I'm going to add documentation about it, I
just didn't have time to write it yesterday. The other possibility is use
only the way that is now used when checked binary, because upload is
currently only for binary fields...
3:10 p.m.
Hi
On Tuesday 04 February 2003 20:51, Marc Delisle wrote:
Michal Cihar wrote:
The crash was just after uploading data, the update query got displayed and
there was binary data in it.
On Monday 03 February 2003 23:00, Marc Delisle
wrote:
Michal,
how do you display the row? I have an application that reads the row in
MySQL,
sends the proper header
and there are no crashes. But maybe this is because of the character
sets when storing
in MySQL. which browser and which kind of files? I had made
tests with .jpg files,
browser IE 6 and Mozilla 1.2.1. No crash at all.
I uploaded small png and it got displayed in SQL and my mozilla 1.2.1
crashed. Konqueror displayed it, but it was nothing nice. If we don't have choice, I agree about the
encoding you added but we
have to document
this somewhere: users will have to know how to decode it in their
applications.
There is no need to decode anything, it's just mysql representation of binary
data. In database there are aways same data. At least it worked so for me.
--
Regards
Michal Cihar
nijel at users dot sourceforge dot net
http://cihar.liten.cz
3:20 p.m.
On Tuesday 04 February 2003 21:08, Michal Cihar wrote:
There is no need to decode anything, it's just
mysql representation of
binary data. In database there are aways same data. At least it worked so
for me.
And it should work so, look at the docs:
http://www.mysql.com/doc/en/Hexadecimal_values.html
http://www.mysql.com/doc/en/BLOB.html
--
Regards
Michal Cihar
nijel at users dot sourceforge dot net
http://cihar.liten.cz
4:21 p.m.
Michal Cihar wrote:
On Tuesday 04 February 2003 21:08, Michal Cihar wrote:
Ok Michal, I will upload some binary the new way and
make some tests with my displaying application.
Marc
There is no need to decode anything, it's just
mysql representation of
binary data. In database there are aways same data. At least it worked so
for me.
And it should work so, look at the docs:
http://www.mysql.com/doc/en/Hexadecimal_values.html
http://www.mysql.com/doc/en/BLOB.html
5 Feb
5 Feb
6:08 a.m.
Marc Delisle wrote:
Michal Cihar wrote:
Ok everything works. I just added some code to avoid
displaying the UPDATE query if there was a binary upload,
now I wonder if we should do the same for the INSERT query?
Marc
On Tuesday 04 February 2003 21:08, Michal Cihar
wrote:
Ok Michal, I will upload some binary the new way and
make some tests with my displaying application.
Marc There is no need to decode anything, it's
just mysql representation of
binary data. In database there are aways same data. At least it
worked so
for me.
And it should work so, look at the docs:
http://www.mysql.com/doc/en/Hexadecimal_values.html
http://www.mysql.com/doc/en/BLOB.html
7897
days inactive
7900
days old
12 comments
5 participants
participants (5)
-
DelislMa＠CollegeSherbrooke.qc.ca -
Marc Delisle
-
Marc Delisle
-
Michal Cihar -
Robin Johnson