Hi,
The current state of 3.0 is quite encouraging. I suggest a round of
testing this summer, followed by -alpha early August, -beta in late
August, -rc1 in mid-September ... and we'll see depending on the feedback.
Marc
Welcome to phpMyAdmin 2.11.8.1, a bugfix-only version containing
normal bug fixes and two security fixes. This version is identical to
2.11.8, except it includes a fix for a notice about "lang".
The security announcement is available as
http://www.phpmyadmin.net/home_page/security.php?issue=PMASA-2008-6
The release notes and download info are available on
http://www.phpmyadmin.net.
Marc Delisle, for the team.
Welcome to phpMyAdmin 2.11.8, a bugfix-only version containing
normal bug fixes and two security fixes.
The security announcement will follow on http://www.phpmyadmin.net.
The release notes and download info are available on
http://www.phpmyadmin.net.
Marc Delisle, for the team.
hehe ...
sf.net awards are given away:
phpMyAdmin is "Best Tool or Utility for SysAdmins"
and "Most Likely to Be the Next $1B Acquisition"
as announced on oscon today
--
Sebastian Mendel
Welcome to phpMyAdmin 2.11.8-rc1, the first release candidate containing
normal bug fixes and two security fixes.
The security announcement will follow on http://www.phpmyadmin.net.
The release notes and download info are available on
http://www.phpmyadmin.net.
Marc Delisle, for the team.
Hi, I am hoping that someone may be able to help me out here...
I recently created a database in phpMyAdmin 2.11.4. As well as the database
I have created a large number of SQL stored procedures. When creating these
stored procedures, I changed the delimeter to $$ as oposed to the standard
";", this is because I have created many PHP 5 scripts which interact with
the database. I have built an ecommerce site and the SQL procedures query
my database (retrieve the products within the catalog of goods).
When I finished developing the site it all work well on my test server -
XAMPP. Recently I signed up with a host company where I have FTP'd all my
coding onto the server. All that is fine. I then uploaded my database onto
an SQL 5 server. I did this by exporting the data in phpMyAdmin into an
.sql file and then uploaded it onto the server by importing the .sql file.
It uploaded no problems but when I checked the server it only imported the
database but not the stored procedures which are key to my site working
properly.
If the hosting company supported the latest version of phpMyAdmin I would be
able to create these SQL stored procedures again and there wouldn't be a
problem, however they don't. Their version of phpMyAdmin does not allow the
user to change the delimeter.
So, sorry for the long-winded story but my question is - is there a way of
exporting the database and all the SQL procedures? I have been over and
over the process of exporting it into a .sql file and it still doesn't work.
There must be a way...or I guess if not I will need to find a hosting
company that supports the latest version of phpMyAdmin.
I would be grateful for any help, I am at the end of my tether and I know
the fault lies nowhere else as everything else works.l
--
View this message in context: http://www.nabble.com/PhpMyAdmin---exporting-SQL-procedures-tp18471661p1847…
Sent from the phpmyadmin-devel mailing list archive at Nabble.com.
Welcome to phpMyAdmin 2.11.7.1, a security fix version.
The security announcement will follow on http://www.phpmyadmin.net.
The release notes and download info are available on
http://www.phpmyadmin.net.
Marc Delisle, for the team.
Right now in trunk we have mootools 1.11, which I tried to use for the
setup script but I hit some nasty bug with DOM selectors and had to
switch to 1.2. Can somebody update the version in trunk to 1.2 and
verify that all scripts depending on this work? mooRainbow got updated
for mootools 1.2 half a year ago so it should be stable despite "beta"
in the name.
Regards,
Piotr
While going through PMA code I found some useless parts in
PMA_fatalError (core.lib.php):
1. I don't see strError in select_lang.lib.php
if (isset($strError)) {
$GLOBALS['strError'] = $strError;
}
2. It's already made global in select_lang.lib.php
if (isset($text_dir)) {
$GLOBALS['text_dir'] = $text_dir;
}
Can somebody check it?
--
Regards,
Piotr