[Phpmyadmin-devel] Improving Sync for Big Tables

[adeel khan]

Hi,
I didnt checked this mail. Sorry Michal i didnt applied to gsoc this time,
because of some constraints. I hope any one else would improve the sync
feature for big tables by going through the idea. I think its workable. As
you have already mentioned that importing use this scheme for assuring
script exec time because the same case applies to importing of data. You
need some assurance that the script should run to a minimal time, and you
can always tell user (which is not the case in import) that how much data
is inserted or else.

adeel

On Thu, Apr 5, 2012 at 6:33 PM, Michal Čihař <michal at cihar.com> wrote:

> Hi
>
> Dne Mon, 26 Mar 2012 02:54:16 +0500
> adeel khan <ak1733 at gmail.com> napsal(a):
>
> > But as we can set the timeout value to a minimum execution time
> > programmatically we would always be assured that we would able to get
> that
> > time for a pass.
>
> This is already used in importing, see libraries/import.lib.php,
> especially PMA_checkTimeout, so it might be turned into more generic
> solution.
>
> --
>        Michal Čihař | http://cihar.com | http://blog.cihar.com
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> 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/20120409/890f6b33/attachment.html>