Is it normal that doing a UPPER() on a VARBINARY field does not work?
CREATE TABLE `t1` (
`f1` varchar(12) NOT NULL default '',
`f2` varbinary(16) NOT NULL default ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
Here, it works on field f1 but not f2. I am using MySQL 4.1.7 and mysqli.
I'm thinking about the "old" Netscape Comunicator (smaller Version 6.0
like 4.78 or so):
should we still supporting this browser with our JS-Functions, CSS-
Styles and interface?
I think, many people are using a newer browser and/or better browser
like Firefox 0.9.3, Mozilla or - of course - InternetExplorer, which is
normaly included as Version 5.0 (and higher) on nearly every MS Windows.
So, for better code-handling and many not supported W3C in Netscape < 6
(no CSS2, no DOM) it may easier for all developers, to stop supporting
the old Netscape Browsers (as we done with PHP version < 4.3).
The PMA version 2.5.7-pl1 works fine with the old Netscape, but the new
PMA versions (> 2.6.0) not really. I've tested - and some things are not
available or won't work correct (multi submit, showing/hiding content on
export page, ...).
Perhabs it would be a good thing to discuss about it, make some infos in
documentation and/or building a browser check (which checks for NS 4 and
gives the user a hint to download a newer browser ;) ).
What are you thinking about this?
finally (after 6 years :) I think we should display the translation of the term "Language"
in each language.
If someone is ever lost on a foreign language page, he should be able
to try the drop-down.
I guess we should handle a bit better security issues. These bugs should be
announced with a bit more details (like when it is exploitable, which
versions are affected and simmilar details). I'd like to have something
simmilar, like xine has:
I wrote how announcement could look like for latest issue. Comments?
Michal Čihař | http://cihar.com
on the edit /insert page, maybe just before the "Insert as a new row / Go back.." dialog,
I would like to add a hint like this:
"Use TAB key to move from value to value, or CTRL+arrows to move anywhere".
please look at bug #1042521 . The problem there is that MySQL wants unix
end of lines, while it is running on Mac. Easiest solution would be to change
PMA_whichCrlf to return \n for mac. As I see other places, there is anyway
code like: (PMA_whichCrlf() == "\n") ? '\n' : '\r\n'), which means we didn't
use \r on any other place than export (and this code was probably wrong for
Mac). Is it okay to do this change?
Michal Čihař | http://cihar.com
Patch level 2 of phpMyAdmin 2.6.0 has been released,
containing a security fix and a few other fixes (see ChangeLog).
Security fix: If PHP is not running in safe mode, a problem in the MIME-based
transformation system (with an "external" transformation) allows to execute
any command with the privileges of the web server's user.
I would like to release a -pl2, which would include the fixes for
- 1037004 (done in HEAD)
- 1036678 (done in HEAD)
- 1033388 (not done)
- possibly other urgent fixes.
This would be released from QA_2_6_0, when 1033388 is done.
I would prefer not to include other fixes that are changing the interface.
If you see other urgent things, please share your thoughts :)