Developers

developers@phpmyadmin.net

2 participants
7003 discussions

[Phpmyadmin-devel] More options for browsing OpenGIS data
by Madhura Jayaratne 24 May '11

24 May '11

Hi all, I have pushed the implementation of the feature 'More options for browsing GIS data' to my repository and you can test it at the demo server[1]. With this, three options have been added to the ‘Options’ section of query result browsing window - To view geometric data in Well Known Text (WKT) format - To view geometric data in Well Known Binary (WKB) format - To view geometric data with Geometric type indication and size (e.g. [GEOMETRY – 2.2KiB]) You can use geometric data in the 'OpenGIS' database to test the feature. If the database is not there by the time you visit, please use the SQL file at [2] to generate the database. Your feedback is highly valued :) Thanks in advance, Madhura Jayaratne [1] http://demo.phpmyadmin.net/gsoc-madhura/index.php [2] https://sourceforge.net/tracker/?func=detail&aid=3300081&group_id=23067&ati…

4 7

[Phpmyadmin-devel] effect of "Remove deprecated function PMA_DBI_get_fields"
by Marc Delisle 24 May '11

24 May '11

Hi, I found one problem with commit fe53e42d1dfff53967ef5c3d6930b1bd9ac4b428. To reproduce, open a table, go to Structure, click Go in the "Create an index" dialog and look at the column names in the Column drop-down. -- Marc Delisle http://infomarc.info

2 1

Re: [Phpmyadmin-devel] Settings page always show restore default value
by Aris Feryanto 24 May '11

24 May '11

On 24 Mei 2011, at 17:17, Marc Delisle <marc(a)infomarc.info> wrote: > Le 2011-05-24 03:19, Aris Feryanto a écrit : >> Hi all, >> >> I've just merged my branch with the current phpMyAdmin official master branch and want to add a new field in the settings page. >> But, when I open settings page, then open some settings tab, I noted that the green arrow button to restore default value is always shown on every fields. >> I also have confirmed this on the phpMyAdmin demo page. >> Is some recent changes cause this? > > Hi Aris, > thanks for noticing this. > > Using the technique explained in [0], it seems that this happened when > upgrading from jQuery 1.4.4 to 1.6.1. I found a link [0] and in the section "Upgrading From 1.5.2 to 1.6.1", there are some notes about the new split of .attr() into two functions: .attr() and .prop(). And I looked into config.js, there are a lot of usage of .attr('tagName'), which is in jQuery 1.6.1 must be accessed through .prop('tagName'). I think we can do a quick replace of .attr('X'), for some X which is now considered as property in jQuery 1.6.1. [0] http://blog.jquery.it/2011/05/12/jquery-1-6-1-released/ -- Aris Feryanto

2 1

[Phpmyadmin-devel] Javascript
by Tyron Madlener 24 May '11

24 May '11

First of all: I hope I'm not too annoying with all my suggestions/questions. Otherwise let me know. My mind is always filled with random ideas ;) I'd like to spark some discussion about noscript-support, particularly after I read that it was a feature suggestion for phpMyAdmin 3 over 3 years ago (http://wiki.phpmyadmin.net/pma/phpMyAdmin_3). I don't know the numbers, but I would assume that nowadays, the percentage of pma users that do not have javascript on must be very low. If there's uncertainty about it, maybe we could start some survey/poll on the phpmyadmin site? (I would offer myself to build it) >From what I can see in the global trends, is that the amount of non-javascript users has been steadily decreasing, with current statistics talking about only 1-3% of internet users having javascript disabled. It feels like a clear disadvantage to me needing to always consider non-javascript users, ending up with programming every feature twice where I could program twice the amount of features instead ;) Having said this, does pma really need noscript-support?

3 9

Re: [Phpmyadmin-devel] Remember the last way user sorted tables
by Aris Feryanto 24 May '11

24 May '11

Hi Piotr, On 24 Mei 2011, at 18:12, Piotr Przybylski <piotr.prz(a)gmail.com> wrote: > 2011/5/24 Aris Feryanto <aris_feryanto(a)yahoo.com>: >> Hi all, >> I've pushed the implementation of feature "Remember the last way user sorted >> tables" when browsing tables. You may try it at the demo server [0]. >> Current implementation only remember the sorting in the session variable. >> So, when you logout and login again, the sorting will be refreshed. >> In order to keep it persistent across session, I will add a new table in >> phpMyAdmin database and store the sorting and maybe other "browsing"-related >> data in there later. > > If you store all data in memory, I think you can use pma_userconfig > table for that, just add a new text column for serialized data. Thank you for your suggestion. I think I will need to store the serialized data per user and per table. But, this is just my current thought. If later, it only needs to be stored per user, then I'll use pma_userconfig table. :) -- Aris Feryanto

2 1

[Phpmyadmin-devel] Table Structure and Details slider
by Marc Delisle 24 May '11

24 May '11

Hi, we got a few reports about this Details slider not being appropriate; one of the reasons is that it's located at the bottom of page. I suggest always showing the sections it contains (Space usage, Row statistics). Target would be 3.4.2. -- Marc Delisle http://infomarc.info

2 1

[Phpmyadmin-devel] Settings page always show restore default value
by Aris Feryanto 24 May '11

24 May '11

Hi all, I've just merged my branch with the current phpMyAdmin official master branch and want to add a new field in the settings page. But, when I open settings page, then open some settings tab, I noted that the green arrow button to restore default value is always shown on every fields. I also have confirmed this on the phpMyAdmin demo page. Is some recent changes cause this? Regards, -- Aris Feryanto

2 1

[Phpmyadmin-devel] Question on i18n
by Tyron Madlener 23 May '11

23 May '11

In most files language strings are being included directly with the __() function, however in server_status.php in the first lines of code are a huge amount of variables being set to the language strings, that are later used. Like those: $strShowStatusDelayed_writesDescr = __('The number of INSERT DELAYED rows written.'); $strShowStatusFlush_commandsDescr = __('The number of executed FLUSH statements.'); $strShowStatusHandler_commitDescr = __('The number of internal COMMIT statements.'); Does that have any particular reason?

2 5

Re: [Phpmyadmin-devel] tracker item
by Herman van Rink 23 May '11

23 May '11

On 23-05-11 12:52, Zarubin Stas wrote: > Hi. > > Thanks. Can you assign this issue to me? I currently can't since your not a member of the sf.net project. I'm not entirely sure but I don't think last years students were added. But to keep updated on the tracker item you can just use the "Monitor" link. > > For the problem with paths - I think the best way to solve it is get > rid of the "./" and "../" in the include/require statements. > And put phpMyAdmin include dir into xml configuration or bootstrap.php I'd prefer as little hard coded configuration as possible. I think the main problem was that sometimes the current corking directory was ./test and sometimes the project root. A good piece of documentation could go along way here... > > -- > Zarubin Stas > > > 23.05.11 13:33, Herman van Rink написав(ла): >> Hi, >> >> >> Could you have a look at: >> https://sourceforge.net/tracker/index.php?func=detail&aid=3170421&group_id=… >> >> >> > -- Met vriendelijke groet / Regards, Herman van Rink Initfour websolutions

1 0

[Phpmyadmin-devel] PMA_DBI_get_columns/fields - which is deprecated?
by Piotr Przybylski 20 May '11

20 May '11

2011/5/19 Dieter Adriaenssens <dieter.adriaenssens(a)gmail.com>: > 2011/5/19 Crack <piotrprz(a)gmail.com>: >> 2011/5/19 Dieter Adriaenssens <dieter.adriaenssens(a)gmail.com>: >> >>> commit 9c170511179 >>> >>> I'm not sure about replacing the obsolete function. I remember Marc >>> telling something about not using 'columns' but 'fields', last summer, >>> so I guess removing the function is a move in the opposite direction. >>> Can you check on the developers mailing list what should be done with >>> this function? >> >> In code comments I saw 'fields' marked as deprecated [1], with >> function's comment telling me to use one of 'columns' variants... > > Yes, I noticed the 'deprecated' status too, but seeing it I remembered > Marc's comment, so I started wondering if this deprecation, or at > least the function name, is still correct. > >> [1] http://repo.or.cz/w/phpmyadmin/crack.git/blobdiff/7d3cd879a496adc27e5e827ef… >> Going public with this, maybe someone will remember :) -- Regards, Piotr Przybylski

3 6

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