>And what about a PMA_phpDie() function?
Why not? But we're not using this feature so
often. As far as I remember, we only display
display error messages when php can't connect
to the MySQL server or when the "mysql_list_db"
can't be used.
That's why I didn't wrote a dedicated function
for php error messages.
Loïc
______________________________________________________________________
Exclusif: 75 euros remboursés sur le pack eXtense Haut Débit de Wanadoo !
Cliquez ici : http://www.ifrance.com/_reloc/mail.exclusif
Hi List,
I was working on the SQL parser, and sat pondering it for a while, and I
wrote up a design note.
I couldn't figure out where to put it, so I filed it under features for
the moment. (I created a category 'Design Notes' there).
In an effort to clean up the feature tracker and make our plans for the
future more clearly laid out, I propose we each try to summarize the
current feature tracker items into a set of design notes, that contain
all the information needed to work on a specific facet of the overall
program.
I've just written up one about the SQL parser. Over the next while I'll
write up notes about the db-config and session-security stuff.
If you have been working on a specific part of PMA a lot, and have plans
for it, write them up in a design note as well.
Alex's discussion the other day about character sets on Macs for
example, is something that needs to be looked at. I think in the long
term a set of functions handling strings will be needed. I started
writing stuff up once before in libraries/string.lib.php. I'll be
commiting a bit more code in there later on to hopefully fix a long
standing multi-byte character bug with the SQL parser.
--
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
Hi List!
Michal wrote:
>I have one question: Why was in libraries/auth/config.auth.lib.php3
>called PMA_mysqldie with sql parameter containing how was
>mysql_connect called?
Well, at the beginning the "PMA_mysqlDie()" function was used
to have a xtml valid and nice MySQL error report. Maybe we
could only add a setting in this function to bypass the parser
when it is called because a PHP function for MySQL failed?
Loïc
______________________________________________________________________
Etudiant: Wanadoo t'offre le Pack eXtense Haut Débit soit 150,92 euros
d'économies ! Clique ici : http://www.ifrance.com/_reloc/mail.etudiant
>Maybe yes, but anyway we should not pass to it passwords
>stored in config file.
Of course ;)
Loïc
______________________________________________________________________
Exclusif: 75 euros remboursés sur le pack eXtense Haut Débit de Wanadoo !
Cliquez ici : http://www.ifrance.com/_reloc/mail.exclusif
Robin,
about bug 621357,
in a query like
UPDATE mytable set myfield = 1
the parser thinks that "set" is a column type.
If I add SET to the list of reserved words, now
the UPDATE statement colorizes ok, but in an ALTER
TABLE with a column type of SET, the SET does not go
orange.
Marc
Hi,
due to a last-minute bug in version 2.3.1 (see last fix in the fix list),
we quickly follow with 2.3.2.
Some improvements:
* upgraded to version 1.51 of the FPDF library
* drop-down choice for foreign keys in Select sub-page
* validation for bookmark insert errors
Some fixes:
* display true row count for InnoDB tables
* parse error in exported dumps
* browser cache problems with Apache 2
* wrong tabindex for linked fields
* cannot change field properties
As usual, download links available at http://www.phpmyadmin.net.
Marc Delisle, for the team.
Hi list,
I'd like to fix bug #547578 finally. The problem is that Mac systems
obviously do not support the ISO-8859 charsets. This is why
Extended-ASCII characters are not displayed correctly on those systems.
There are three possible ways to fix this:
1) We could add a set of new language files that are encoded with the
Mac charsets. Unfortunatly, this would result in larger distribution
packages, but it is the only way to have this problem fixed without
using iconv or recode.
2) We could convert all message strings after having loaded the specific
language file if a Mac client has been detected. This would increase the
server charge because we would convert much more strings than we need
to. Furthermore, the iconv or the recode php extension have to be loaded
for this variant.
3) We could convert the message strings when displaying them. A huge
update would be required here because we need to replace each call of a
$str variable by a call of a new function that converts the string if
nessecary. Like in variant 2, either inconv or recode need to be loaded.
Any suggestions?
Alexander
Hi
I've made fix for this bug, but I have one question: Why was in
libraries/auth/config.auth.lib.php3 called PMA_mysqldie with sql parameter
containing how was mysql_connect called? Then it made problems to SQL
parser (only when IP address was used as host) and it reported error,
where the password from config was shown.
Michal
