On Wed, Mar 23, 2011 at 5:29 PM, Marc Delisle <marc@infomarc.info> wrote:
Madhura Jayaratne a écrit :
> Hi Mark,
>
> On Tue, Mar 22, 2011 at 6:06 PM, Marc Delisle <marc@infomarc.info
> <mailto:marc@infomarc.info>> wrote:
>
>     Hi,
>     as part of solving this bug [0]
>     please test this patch [1] against current master and report in the
>     patch tracker.
>
>
> I tested the patch. It seems to work fine.

Thanks, patch merged.
>
>     We'll still need to find a way to display the updated timestamp, but at
>     least with this patch the timestamp is updated in the modified row.
>
> I guess we can do a query on the updated timestamp and feed it to the
> front end with the ajax response.
> However I would like to know the possibility of doing a query on the
> whole tuple and feeding it to the front end. This way we will be able to
> avoid number of code duplications we have now.

I think it could be done. At this point in js/sql.js we have the "where
clause" that was used for the UPDATE so maybe it could be used to
generate a small result set (just this row) and call
PMA_displayTableBody() in a new Ajax mode.

However we'll have to be careful about parameters in the "where clause" being changed due to the inline edit

--
Thanks and Regards,

Madhura Jayaratne