Developers

developers@phpmyadmin.net

7002 discussions

phpMyAdmin 4.6.0 is released
by Isaac Bennetch 22 Mar '16

22 Mar '16

Welcome to phpMyAdmin 4.6.0, a regular maintenance release including over 60 new features and bug fixes. Please note that this release ends support for old versions of Microsoft Internet Explorer, which are no longer supported by Microsoft. There is a new configuration directive, $cfg['Servers'][$i]['ssl_verify'] which is useful in some cases with self-signed certificates. The ForceSSL and PmaAbsoluteUri configuration directives have been removed (the functions of both of these should better be handled by the webserver than the application). A complete list of new features and bugs that have been fixed is available in the ChangeLog file or changelog.php included with this release. A few highlights: * Allow setting routine-wise privileges * UI for defining partitioning in create table window * Support JSON data type * Editing partitions in table Structure * Copy results to clipboard * Reactivate cut&paste possibility in print view * Display binary strings as text if they are valid UTF-8 * Copy multiple tables to database * Show MySQL error messages in user language * Add new configuration directive 'ssl_verify' for self-signed certificates with mysqlnd and PHP >=5.6 * Remove ForceSSL and PmaAbsoluteUri configuration directives (these are better handled by proper webserver configuration) * Fixed several bugs relating to exporting, particularly with DEFAULT and COMMENT fields There are many more improvements; please refer to the ChangeLog for full details. As always, downloads are available at http://www.phpmyadmin.net As always, thanks to our sponsors for helping to make this work possible! The phpMyAdmin Team

1 0

Any blockers for phpMyAdmin 4.6.0 ?
by Isaac Bennetch 22 Mar '16

22 Mar '16

Hello, As you know, we're quickly approaching the scheduled release date for 4.6.0. Does anyone see any bugs that might block the release? There currently aren't any tagged at https://github.com/phpmyadmin/phpmyadmin/milestones but since we're about a day away from the scheduled release I thought I should check in. If there are no objections, I'll probably plan to release 4.6.0 in about 26 hours from now. Isaac

3 4

DCO for motranslator and sql-parser
by Isaac Bennetch 20 Mar '16

20 Mar '16

Hi, We probably should add the DCO to these two sub-projects (motranslator and sql-parser) and require the same contribution guidelines (by which I mean signed off by a real name), do you agree? I can add those files and document those steps if no one disagrees.

3 2

SQL parser debugging
by Michal Čihař 18 Mar '16

18 Mar '16

Hi all to make easier working and debugging the SQL parser, I've added two simple command line utilities to syntax highlight and lint the query. I hope you will find them useful :-). For example the lint: $ ./bin/lint-query --query 'select (SELECT name FROM mysql.help_category WHERE help_category_id = 1) as name, case when country = "India" then 1 else 0 end as country_flag FROM ( select "India" as country ) a;' #1: An alias was expected. (near " " at position 75) #2: Unrecognized keyword. (near "name" at position 76) #3: Unexpected token. (near "," at position 80) #4: Unrecognized keyword. (near "case" at position 82) #5: Unrecognized keyword. (near "when" at position 87) #6: Unexpected token. (near "country" at position 92) #7: Unexpected token. (near "=" at position 100) #8: Unexpected token. (near ""India"" at position 102) #9: Unrecognized keyword. (near "then" at position 110) #10: Unexpected token. (near "1" at position 115) #11: Unrecognized keyword. (near "else" at position 117) #12: Unexpected token. (near "0" at position 122) #13: Unrecognized keyword. (near "end" at position 124) #14: Unrecognized keyword. (near "as" at position 128) #15: Unexpected token. (near "country_flag" at position 131) #16: An expression was expected. (near "(" at position 149) #17: Unexpected token. (near "(" at position 149) #18: This type of clause was previously parsed. (near "select" at position 151) #19: Unexpected token. (near ")" at position 177) #20: Unexpected token. (near "a" at position 179) -- Michal Čihař | http://cihar.com/ | https://weblate.org/

1 0

(no subject)
by Sandal Shukla 10 Mar '16

10 Mar '16

How to solve this error in phpmyadmin in vesta cp Connection for controluser as defined in your configuration failed.

1 0

GSoC 2016 Participation
by Amos Nzivu 09 Mar '16

09 Mar '16

Hey, Kindly confirm if phpMyAdmin was shortlisted in this year's Google summer of Code participating organizations.Have been interested by idea from phpMyAdmin ideas List but phpMyAdmin is not appearing in the list of organizations in official Google of Summer website. Looking foward to reading from you. Cheers, Amos Nzivu.

2 1

Monthly meeting on Wednesday
by Isaac Bennetch 09 Mar '16

09 Mar '16

Hi, the monthly IRC meeting is scheduled for this Wednesday. We don't have many topics this month[1]. Hope to see you there. 1 - https://wiki.phpmyadmin.net/pma/2016-03_Meeting

2 4

sql-parser documentation
by Isaac Bennetch 07 Mar '16

07 Mar '16

Hi, What format for documentation do you feel would be best for the sql-parser library? We could do the .rst format that phpMyAdmin uses, or we could use MarkDown which would be directly interpreted by Github. I'm rather indifferent about it, and since it's going to be for developers rather than end users we might want to go a different direction. Any opinions about this?

2 1

Parenthesis in REPLACE query
by Isaac Bennetch 07 Mar '16

07 Mar '16

Does this look like a parser problem? http://stackoverflow.com/questions/35568587/phpmyadmin-4-5-4-unexpected-tok… Isaac

2 2

Relating phpMyAdmin release versions with library versions
by Isaac Bennetch 02 Mar '16

02 Mar '16

Hi, I have a question about library version numbers when we perform a release of phpMyAdmin. For example, in composer.json we currently require sql-parser 3.3 or newer, which is good, because then any newer fixes get incorporated on release without needing to constantly chase the version in composer.json. However, if someone is testing with release 4.6.0-rc2 and we fix something in sql-parser, a developer checking out the git tag RELEASE_4_6_0RC2 will get the updated sql-parser. It seems the only way to test with the sql-parser version included in a release is to actually download the released tarball, whereas in the past we were able to simply checkout the corresponding git tag. It feels like a workaround instead of a solution, but I'm not sure that we can realistically do anything to improve it. Furthermore, the demo servers will always be running the most up-to-date sql-parser release, even when the corresponding release has an older version (at least, updated as often as pma-demo-update is called), so asking a user to test against the demo server takes on a slightly different meaning when debugging. Does this sound right, and is it really anything to worry about in the scheme of things? Or am I getting concerned about a minor thing? Thanks Isaac

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Developers