Developers January 2017

developers@phpmyadmin.net

7 participants
26 discussions

Re: [phpMyAdmin Developers] phpmyadmin new version
by Michal Čihař 06 Jan '17

06 Jan '17

Hello Don't get me wrong, but we really can not release patch release for every bug we fix. We do that only for things like data corruption or bugs affecting many users. You're talking about https://github.com/phpmyadmin/phpmyadmin/issues/12 786 which was reported by you and nobody else did complain about that issue... On the other side, there are currently 46 issues fixed for 4.6.6, many of them being more important and affecting more users: https://github.com/phpmyadmin/phpmyadmin/milestone/228?closed=1 -- Michal Čihař | https://cihar.com/ | https://weblate.org/ Flavius Nopcea píše v St 04. 01. 2017 v 17:16 +0200: > feeling disappointed... > > if you have a server with only a few databases then I agree with > you... > > > On 04.01.2017 17:12, Michal Čihař wrote: > > Hi > > > > Flavius Nopcea píše v Út 03. 01. 2017 v 10:34 +0200: > > > yes, but what about patch releases? > > > > > > you keep the search functionality not working for 2 months? > > > > So far we didn't consider this bug to be important enough for a > > patch > > release. > > > >

1 0

Re: [phpMyAdmin Developers] phpmyadmin new version
by Michal Čihař 04 Jan '17

04 Jan '17

Hi Flavius Nopcea píše v Út 03. 01. 2017 v 10:34 +0200: > yes, but what about patch releases? > > you keep the search functionality not working for 2 months? So far we didn't consider this bug to be important enough for a patch release. -- Michal Čihař | https://cihar.com/ | https://weblate.org/

1 0

Re: [phpMyAdmin Developers] phpmyadmin new version
by Michal Čihař 03 Jan '17

03 Jan '17

Hello Flavius Flavius Nopcea píše v Út 03. 01. 2017 v 09:24 +0200: > Hi Michal, > > pls release a new version of phpmyadmin, > the last one has the search box broken. > > also, pls try to release new versions more often. > thanks With monthly release schedule we got complains about releases happening too often, so we have settled down on two months release schedule for now. The 4.6.6 should be out in two weeks. You can see the roadmap on GitHub: https://github.com/phpmyadmin/phpmyadmin/milestones -- Michal Čihař | https://cihar.com/ | https://weblate.org/

1 0

Suggestion regarding gsoc idea "Facilitate drag and drop of columns between tables"
by Osaid Nasir 02 Jan '17

02 Jan '17

Hi, I am Osaid and I go by the name ragnerok on github. I saw that "Facilitate drag and drop of columns between tables " was a gsoc idea . However I think that rather than having a drag and drop method it would be a lot better if we could add another "with selected:" option saying something like "MOVE TO OTHER TABLE" That way if a person wants the same row in 2 different tables he can easily do it with this action plus if he wanted to move then drop he can do that too Also I wanted to know if this alone was enough as a gsoc project ? Thanks

1 0

representation of 'text' fields
by Norbert Zawodsky 02 Jan '17

02 Jan '17

Hi everyone! after using pma for years now, I yesterday registered to this mailing-list hoping to get some help or info.. Some days ago I upgraded from 4.6.3 to 4.6.5.2 and immediately noticed a new, very annoying behavior. I have tables with fields of type "text". Previous pma rendered these fields as "normal" single-line text fields. Eventually becoming multilined if they didn't fit into space. The new pma (4.6.5.2) now renders DB text fields as a big box (approx space for 6 lines). This wastes a lot of screen space, leads to lot of scrolling and making everything confusing. For example with previous version I saw nearly 25 records on the screen, now I'm seeing 5. Is there a way to config this behaviour? I googled a lot but didn't find any useful information. Norbert

2 1

View pagination behavior - Is this a bug?
by Isaac Bennetch 02 Jan '17

02 Jan '17

When looking at a view that only has a few rows, the pagination arrows are shown (next page, last page, etc); when looking at the corresponding table, they aren't there. It is ideal if they aren't shown, but I don't know if that is possible to determine with a view. Also, I get the message "Current selection does not contain a unique column. Grid edit, Edit, Copy and Delete features may result in undesired behavior. " -- even though my view is based on a table that does contain a primary key; my view is simply `select * from tbl` and the table is just two columns; an autoincrement int and a varchar. Again, I don't know whether this is something that is a limitation of the view or if we can improve behavior here. Thanks

2 1

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 January 2017