[Phpmyadmin-devel] Bug #4301: need suggestion

Smita kumarismita62 at gmail.com
Mon Mar 3 18:24:44 CET 2014


On Mon, Mar 3, 2014 at 10:08 PM, Atul Pratap Singh <
atulpratapsingh05 at gmail.com> wrote:

> On 3/3/14, Smita <kumarismita62 at gmail.com> wrote:
> > Hi,
> >
> > I was looking at the bug http://sourceforge.net/p/phpmyadmin/bugs/4301/. I
> > think, If the query execution is not redirecting page, ie it's happening
> on
> > the same page via an ajax request then there are two ways we can approach
> > it.
> > 1.  Append an another Query box below previous Query box for all the
> > following requests. So in this case, we'll have separate query boxes for
> > each operation performed on the page.
> Smita,
> Similar behavior occurs when:-
> In Browse mode, click on "Edit" in a table row => On edit page change
> something and click Go => see two SQL query boxes with UPDATE query
> box on top not below.
>

Yeah, skipping UPDATE query sounds good to me and In the success popup I
think it's fine to just show the updation success message?

But IMO, we could skip showing UPDATE query altogether if the user did
> it with grid edit.  Or we could also show SQL query momentarily in the
> success message that pops up.
>
> > 2.  Append the query itself with separator semicolon in the same existing
> > query box. In this case we'll have same just one Query box having all the
> > Queries appended with separator semicolon.
> >
> > Please let me know if any concern, and what approach we can take to solve
> > the same ?
> >
> > Fixing the bug will also make sure that user will have list of all the
> > queries performed on relation in order that resulted into the results
> > displayed on the page.
> >
> If you mean showing a sort of history of SQL queries, I don't think
> main Browse page is suitable place for that.
>
>
> Regards
> --
> Atul Pratap Singh
> http://blog.atulsisodia.in/
>

Thanks and Regards
Smita Kumari

>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Phpmyadmin-devel mailing list
> Phpmyadmin-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20140303/66c739e4/attachment.html>


More information about the Developers mailing list