Hi phpmyadmin developers,
I just downloaded 4.5.0-beta1. I love that you are using the ALTER USER command from 5.7!
I have some specific 5.7 features to mention that you may be able to make use of:
1) The server now supports a list of disabled_storage_engines (these still “work” but no new tables can be created). It might make sense to remove them from the drop-down-list or make them appear greyed out. They also appear under “ENGINES” the same as others currently.
2) The STATUS > PROCESSLIST is currently using SHOW PROCESSLIST. In MySQL 5.7, there will be SELECT * FROM sys.x$processlist or SELECT * FROM sys.x$sessions (user connections only). This has some added context (transactions open, memory usage etc) and the command itself uses fewer locks than SHOW PROCESSLIST. Here is an example of output:
https://github.com/MarkLeith/mysql-sys/blob/development/views/p_s/sessions.s...
3) The datatype JSON does not appear to be added yet. 5.7.8 added this native type with ~20 JSON manipulation functions.
- Morgan
Le 2015-08-26 13:18, Morgan Tocker a écrit :
Hi phpmyadmin developers,
I just downloaded 4.5.0-beta1. I love that you are using the ALTER USER command from 5.7!
I have some specific 5.7 features to mention that you may be able to make use of:
- The server now supports a list of disabled_storage_engines (these
still “work” but no new tables can be created). It might make sense to remove them from the drop-down-list or make them appear greyed out. They also appear under “ENGINES” the same as others currently.
- The STATUS > PROCESSLIST is currently using SHOW PROCESSLIST. In
MySQL 5.7, there will be SELECT * FROM sys.x$processlist or SELECT * FROM sys.x$sessions (user connections only). This has some added context (transactions open, memory usage etc) and the command itself uses fewer locks than SHOW PROCESSLIST. Here is an example of output:
https://github.com/MarkLeith/mysql-sys/blob/development/views/p_s/sessions.s...
- The datatype JSON does not appear to be added yet. 5.7.8 added
this native type with ~20 JSON manipulation functions.
- Morgan
Hi Morgan,
thanks for the insight. phpMyAdmin 4.5 is feature frozen but we'll see what we can do for 4.6.
On Thu, Aug 27, 2015 at 3:18 AM, Morgan Tocker morgan.tocker@oracle.com wrote:
Hi phpmyadmin developers,
I just downloaded 4.5.0-beta1. I love that you are using the ALTER USER command from 5.7!
I have some specific 5.7 features to mention that you may be able to make use of:
- The server now supports a list of disabled_storage_engines (these still
“work” but no new tables can be created). It might make sense to remove them from the drop-down-list or make them appear greyed out. They also appear under “ENGINES” the same as others currently.
- The STATUS > PROCESSLIST is currently using SHOW PROCESSLIST. In MySQL
5.7, there will be SELECT * FROM sys.x$processlist or SELECT * FROM sys.x$sessions (user connections only). This has some added context (transactions open, memory usage etc) and the command itself uses fewer locks than SHOW PROCESSLIST. Here is an example of output:
https://github.com/MarkLeith/mysql-sys/blob/development/views/p_s/sessions.s...
- The datatype JSON does not appear to be added yet. 5.7.8 added this
native type with ~20 JSON manipulation functions.
Support for JSON data type can be tracked at
https://github.com/phpmyadmin/phpmyadmin/issues/11438
On Aug 27, 2015, at 3:49 AM, Madhura Jayaratne madhura.cj@gmail.com wrote:
- The datatype JSON does not appear to be added yet. 5.7.8 added this native type with ~20 JSON manipulation functions.
Support for JSON data type can be tracked at https://github.com/phpmyadmin/phpmyadmin/issues/11438
Excellent! This is the only high priority change, since editing tables with a JSON column currently cause errors.
Le 2015-08-27 10:34, Morgan Tocker a écrit :
On Aug 27, 2015, at 3:49 AM, Madhura Jayaratne madhura.cj@gmail.com wrote:
- The datatype JSON does not appear to be added yet. 5.7.8 added this native type with ~20 JSON manipulation functions.
Support for JSON data type can be tracked at https://github.com/phpmyadmin/phpmyadmin/issues/11438
Excellent! This is the only high priority change, since editing tables with a JSON column currently cause errors.
Morgan, see issue 11438 for the PHP problems we have.
Hi Marc,
On Aug 28, 2015, at 12:46 PM, Marc Delisle marc@infomarc.info wrote:
see issue 11438 for the PHP problems we have.
Thanks for the heads up!
I’ve forwarded it to our PHP driver guys internally.
They may ask for a bug to be filed on bugs.php.net so it can be tracked. I did a quick search and it doesn’t seem like one has been reported yet. Did you want the honours of filing?
- Morgan
Le 2015-08-28 13:18, Morgan Tocker a écrit :
Hi Marc,
On Aug 28, 2015, at 12:46 PM, Marc Delisle marc@infomarc.info wrote:
see issue 11438 for the PHP problems we have.
Thanks for the heads up!
I’ve forwarded it to our PHP driver guys internally.
They may ask for a bug to be filed on bugs.php.net so it can be tracked. I did a quick search and it doesn’t seem like one has been reported yet. Did you want the honours of filing?
https://bugs.php.net/bug.php?id=70384
On Aug 28, 2015, at 2:15 PM, Marc Delisle marc@infomarc.info wrote:
They may ask for a bug to be filed on bugs.php.net so it can be tracked. I did a quick search and it doesn’t seem like one has been reported yet. Did you want the honours of filing?
Thanks Marc!
I’ve given Johannes and Andrey the heads up.
On Aug 28, 2015, at 2:40 PM, Morgan Tocker morgan.tocker@oracle.com wrote:
They may ask for a bug to be filed on bugs.php.net so it can be tracked. I did a quick search and it doesn’t seem like one has been reported yet. Did you want the honours of filing?
I have a followup workaround suggestion for this bug. JSON data can be cast as a string type on extraction:
select id, CAST(jsoncol as CHAR) from marctable;
While I trust that the bug will be fixed, there is obviously some lag in users upgrading their PHP versions. So I wonder if it is preferable to implement the workaround or conditional checking for a specific PHP version >= fix version?
(Best for you to determine obviously!)
- Morgan
Le 2015-09-02 14:16, Morgan Tocker a écrit :
On Aug 28, 2015, at 2:40 PM, Morgan Tocker morgan.tocker@oracle.com wrote:
They may ask for a bug to be filed on bugs.php.net so it can be tracked. I did a quick search and it doesn’t seem like one has been reported yet. Did you want the honours of filing?
I have a followup workaround suggestion for this bug. JSON data can be cast as a string type on extraction:
select id, CAST(jsoncol as CHAR) from marctable;
While I trust that the bug will be fixed, there is obviously some lag in users upgrading their PHP versions. So I wonder if it is preferable to implement the workaround or conditional checking for a specific PHP version >= fix version?
(Best for you to determine obviously!)
Hi Morgan,
well, the goal is not just to make the test script work, but everywhere in phpMyAdmin where we SELECT. This might be problematic and would introduce some overhead.
Also, even if we fix this in phpMyAdmin, users who poll the database with their own script will face the same problem, so it would be really better for everyone if the PHP bug was fixed.
Hi Marc,
On Sep 2, 2015, at 4:50 PM, Marc Delisle marc@infomarc.info wrote:
Also, even if we fix this in phpMyAdmin, users who poll the database with their own script will face the same problem, so it would be really better for everyone if the PHP bug was fixed.
This is true of course, if the application is also PHP based.
I was not implying that the PHP bug would not be fixed - just suggesting that there is a workaround for php versions which predate the fix, since upping the minimum version requirements is not easy.
- Morgan
On Thu, Aug 27, 2015 at 3:18 AM, Morgan Tocker morgan.tocker@oracle.com wrote:
Hi phpmyadmin developers,
I just downloaded 4.5.0-beta1. I love that you are using the ALTER USER command from 5.7!
I have some specific 5.7 features to mention that you may be able to make use of:
- The server now supports a list of disabled_storage_engines (these still
“work” but no new tables can be created). It might make sense to remove them from the drop-down-list or make them appear greyed out. They also appear under “ENGINES” the same as others currently.
https://github.com/phpmyadmin/phpmyadmin/issues/11456
- The STATUS > PROCESSLIST is currently using SHOW PROCESSLIST. In MySQL
5.7, there will be SELECT * FROM sys.x$processlist or SELECT * FROM sys.x$sessions (user connections only). This has some added context (transactions open, memory usage etc) and the command itself uses fewer locks than SHOW PROCESSLIST. Here is an example of output:
https://github.com/MarkLeith/mysql-sys/blob/development/views/p_s/sessions.s...
- The datatype JSON does not appear to be added yet. 5.7.8 added this
native type with ~20 JSON manipulation functions.
- Morgan
-- Morgan Tocker MySQL Community Manager Oracle Canada - Hardware and Software, Engineered to Work Together. Office: Toronto, Canada
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
-
Madhura Jayaratne -
Marc Delisle -
Morgan Tocker