Developers

developers@phpmyadmin.net

7004 discussions

[Phpmyadmin-devel] phpMyAdmin 3.5.1-rc1 is released
by Marc Delisle 24 Apr '12

24 Apr '12

Welcome to the first release candidate for phpMyAdmin 3.5.1, a bugfix release. Details will appear on http://phpmyadmin.net. In a hurry? you can visit http://sourceforge.net/projects/phpmyadmin to download. Marc Delisle, for the team

1 0

[Phpmyadmin-devel] Announcing phpMyAdmin's GSoC 2012 projects and students
by Michal Čihař 24 Apr '12

24 Apr '12

We would like to announce that phpMyAdmin will have six projects in Google Summer of Code 2012. We've received 38 applications, what is much more than we are able to mentor and it was sometimes a tough process to select the best ones. We would like to thank all people who have applied, for their time and energy; we hope that not being selected for this summer will not prevent them from contributing to phpMyAdmin. The final six chosen projects are: * Automated Testing by Yasitha Pandithawatta * Refactoring Insert/edit, Operations, Privilege and Structure sections in phpMyAdmin by Thilina Buddika Abeyrathna * Refactoring: Displaying query results by Chanaka Indrajith * Refactoring: Table search, Db search, Multi-table query by Atul Pratap Singh * Removal of frames and integration of a new navigation system into phpMyAdmin by Rouslan Placella * Two approaches for Plugins and OOP and an object-oriented properties system by Alex Marin Good luck to all students to complete all the projects successfully. -- Michal Čihař for the phpMyAdmin team

1 1

[Phpmyadmin-devel] GSOC 2012
by Thilina Buddika Abeyrathna 24 Apr '12

24 Apr '12

Hi, I have selected for Google summer of code 2012 under "Refactoring insert/edit, Privileges, Structures, Operation sections in PMA" project idea. Thank you all who has helped me to accept. Specially Marc, you have helped me lot to prepare the proposal and patches. And my gratitude goes to all the PMA members. Now it is time to work with this project and this is the community bonding period of the time line. I will very thankfull If you have any suggestion for me to start to working and more familiar with pma. -- Regards. Thilina Buddika Abeyrathna, Department of Computer Engineering, Faculty Of Engineering, University of Peradeniya, Sri Lanka.

2 2

[Phpmyadmin-devel] wiki and configuration directives
by Marc Delisle 23 Apr '12

23 Apr '12

Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue. I find it difficult and error-prone to document configuration directives at two places: Documentation.html and the wiki [0]. My suggestion is to remove it from the wiki. [0] http://wiki.phpmyadmin.net/pma/Config -- Marc Delisle http://infomarc.info

4 5

[Phpmyadmin-devel] Report from Percona Live MySQL 2012 & Thanks to Yosun Chang
by Robin H. Johnson 23 Apr '12

23 Apr '12

Hi all, This is my report back from the Percona MySQL conference. This is my 5th year representing PMA at the MySQL conference: I've been there 2012, 2011, 2010, 2009, 2006 (Marc did it solo in 2007/2008 as I couldn't afford it or had conflicts). I realize that I've also been involved with phpMyAdmin for more than 11 years now. My first patch went in 2001/04/29 and I was on the mailing lists prior to the SourceForge move. I'd like to extend a special thank you to Yosun Chang. (BCC'd). She saw our booth last year: http://yfrog.com/h0avrihj Blogged about designer mode: http://yosun.me/2011/04/13/enabling-phpmyadmin-designer-mode-for-ajax-view-… And then this year she came back and loaned us a monitor to help show off features, and lend a hand on the first night: https://twitter.com/#!/Yosun/status/189863107638726657/photo/1 She's also all-around awesome and has a little startup: http://www.kubikulo.com/ General: - The GIS functionality was a hit, along with the always popular DB designer and charts. - As per previous years, there are two types of people that came to the booth: - Those to give us kudos as they already use PMA - those that were lurking the conference, and often haven't used MySQL at all before, if they were even a tech type. Specific list of bugs & feature requests: - DB Designer and other tools that require the PMAdb to be created need to be easier to get going. Maybe include the ability to specify your MySQL root credentials and use them to create a database, import the schema, create the PMA user? - It needs to be possible to put PMAdb on a different server. For if you're connecting PMA to a readonly replication slave, and you cannot save your bookmarks or query history. - Charts functionality is popular, but painful to use sometimes: An example from the GIS sample data I was using: Creating a chart of the population of regions of Mexico: You have to create a view with name/population first, and chart that. It was simply not doable with the base table. - User auth is still a holdback. There is demand for a transformation function: auth(user, password[, server[, token]]) does validation, and on success, returns (mysqluser, mysqlpassword), which is used to connect to MySQL. The transformation function should have some common variants, but also be able to plug in something else custom (eg LDAP). - Some users complained that the versions of PMA deployed by cpanel and Rackspace are out-of-date and/or crippled. User management esp was noted as crippled. - Engine support: Tokutek asked about what was needed to get their engine listed in the create table dropdown. - Replication status: can we include the stats from the Maatkit/Percona Toolkit heartbeat app, and/or possible other tools? - The DB Designer had some feature requests too: - Some rough attempt at an initial layout solution - Auto-save layout changes - Create table opening in a new tab - PR material needed: We've got the artwork material we used for the banner in 2005, and the team shirts made at the same time, but not much other selection of open-format vector artwork for usage in conference programs and other promotional material. I've seen jpegs of newer logo materials, but very little by way of vector source artwork. Negatives: - Our banner, originally printed for the first ever team meeting back at LinuxTag 2005 in Karlsruhe, got lost at the end of this trip :-(. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robbat2(a)gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85

3 2

Re: [Phpmyadmin-devel] Bug #3441722 - Where should we store the description?
by Willian Gustavo Veiga 20 Apr '12

20 Apr '12

Hi Michal Čihař, how are you doing? > Yes function for getting description for type in libraries/data_mysql.inc.php would be IMHO best. I've made it this way. Pull request done: https://github.com/phpmyadmin/phpmyadmin/pull/42 Drizzle needs better descriptions. Thank you for your time.

2 1

Re: [Phpmyadmin-devel] Bug #3441722 - Where should we store the description?
by Willian Gustavo Veiga 20 Apr '12

20 Apr '12

Rouslan, first of all thank you for your time. > although I'm not sure if the descriptions belong in the configuration array. So, what do you suggest? You're right Rouslan, it shouldn't be part of the configuration array. Maybe a function that returns these data ... > Also, if you're preparing a pull request, you might want to add the type descriptions for Drizzle as well. Great, i'll do the same for the Drizzle. Thank you very much. I really appreciate your help Rouslan.

2 1

[Phpmyadmin-devel] Bug #3441722 - Where should we store the description?
by Willian Gustavo Veiga 19 Apr '12

19 Apr '12

I've been trying to fix the bug #3441722 <http://sourceforge.net/tracker/?func=detail&aid=3441722&group_id=23067&atid…> and I have few questions. I've stored descriptions in /libraries/data_mysql.inc.php: $cfg['ColumnTypesDescription'] = !empty($cfg['ColumnTypesDescription']) ? $cfg['ColumnTypesDescription'] : array( 'TINYINT' => 'A very small integer. The signed range is -128 to 127. The unsigned range is 0 to 255.', 'SMALLINT' => 'A small integer. The signed range is -32768 to 32767. The unsigned range is 0 to 65535.', 'MEDIUMINT' => 'A medium-sized integer. The signed range is -8388608 to 8388607. The unsigned range is 0 to 16777215.', 'INT' => 'A normal-size integer. The signed range is -2147483648 to 2147483647. The unsigned range is 0 to 4294967295.', 'BIGINT' => 'A large integer. The signed range is -9223372036854775808 to 9223372036854775807. The unsigned range is 0 to 18446744073709551615.', 'DECIMAL' => 'A packed "exact" fixed-point number. M is the total number of digits (the precision) and D is the number of digits after the decimal point (the scale). The decimal point and (for negative numbers) the "-" sign are not counted in M. If D is 0, values have no decimal point or fractional part. The maximum number of digits (M) for DECIMAL is 65. The maximum number of supported decimals (D) is 30. If D is omitted, the default is 0. If M is omitted, the default is 10.', 'FLOAT' => 'A small (single-precision) floating-point number. Permissible values are -3.402823466E+38 to -1.175494351E-38, 0, and 1.175494351E-38 to 3.402823466E+38. These are the theoretical limits, based on the IEEE standard. The actual range might be slightly smaller depending on your hardware or operating system.', // .... I don't think these description should be there, but I don't know the "right" place. Maybe we should create a database table or a file to store these information. I've implemented some code to fix this bug and it's working, maybe I should do a pull request. I am pretty new to PhpMyAdmin's codebase. Thank you very much and sorry about my english.

2 1

[Phpmyadmin-devel] Proposal: Refactoring Designer/schema integration
by Adnan 19 Apr '12

19 Apr '12

hello Michal, I have submitted my proposal, please have a look at it. Give your important input So I could edit my proposal then. Thanks -- Muhammad Adnan Twitter: @hiddenpearls I blog too do u know ? http:// www.imblog.info Failure takes you higher than success ..! you sell code, I sell my brain.

5 11

[Phpmyadmin-devel] Error on db privileges page in master
by Rouslan Placella 19 Apr '12

19 Apr '12

Hi all, I just noticed a strange behaviour when you click on the db privileges tab. You get the correct page, but the breadcrumbs, menubar and navigation think that you are at server level, rather than at db level. Git-bisect said: fa02a8669ddceeb77367a420a1a84dd303a2b297 is the first bad commit commit fa02a8669ddceeb77367a420a1a84dd303a2b297 Author: Marc Delisle <marc(a)infomarc.info> Date: Sun Mar 4 07:31:37 2012 -0500 All cases of globalizing $_GET variables are hopefully covered by now Bye, Rouslan

2 1

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