[Phpmyadmin-devel] Bug #4301: need suggestion

[Smita]

Okay, so I'm keeping the update query above the select query statement same
as it shows on page that comes when we click on edit, make changes and
click go.

Regards
- Smita Kumari


On Tue, Mar 4, 2014 at 10:55 PM, Marc Delisle <marc at infomarc.info> wrote:

> Smita a écrit :
> > So for now, Should I skip the update query and just show the initial
> select
> > statement instead?
>
> My preference would be to show both: the update query and the select query.
> >
> > Regards
> > Smita Kumari
> >
> >
> > On Tue, Mar 4, 2014 at 6:57 PM, Marc Delisle <marc at infomarc.info> wrote:
> >
> >> Atul Pratap Singh a écrit :
> >>> On 3/3/14, Smita <kumarismita62 at gmail.com> wrote:
> >>>> 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?
> >>>>
> >>> Yes, for the purpose of this bug, its fine for me to skip showing the
> >> query.
> >>> But indeed we need to have a full SQL log/history as well.
> >>>
> >>> Marc,
> >>> Can we modify [0] to include implementing a full SQL log/history
> >>> feature as suggested by Michal ?
> >>>
> >>> [0] https://sourceforge.net/p/phpmyadmin/feature-requests/1492/
> >>>
> >>>
> >>> Regards
> >> Atul,
> >> yes, I'll modify it as well as the GSoC ideas list.
> >>
> >> --
> >> Marc Delisle
> >> http://infomarc.info | http://phpmyadmin.net
>
>
>
> --
> Marc Delisle
> http://infomarc.info | http://phpmyadmin.net
>
>
> ------------------------------------------------------------------------------
> 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/20140305/a5774cec/attachment.html>