mysql q

[ik]

Hi, I think you tackle it wrong.

If there is no need for accessing the database all the time, why not cache
the result in tools such as Memcached or Redis ?
If they are different clients (as in agents), then there are other tools at
your disposal, such as Varnish, that create cached version for the web.

Secondly, the MySQL/MariaDB triggers really basics if you compare them to
PG and Fb (true open source solutions), not to mention non open source
databases such as SQL Server and Oracle.

Third, try to see how you can optimize the page. If there is no need for
constant data reading, why does it constantly refresh itself ?

Ido


On Sun, Nov 17, 2013 at 10:18 AM, Erez D <erez0001 at gmail.com> wrote:

> hello
>
> i have a web page that refreshes all the time to display things from a
> mysql database which is updated from time to time.
> however. this meens a lot of un-needed acesses to the database. and this
> refresshing page may be openede by many browsers. causing a huge load on
> the database.
>
> i know mysql supports triggers, but it seems this is only internal (i.e.
> trigger may do a query, usually an "update" query, but this is not what i
> need).
>
> I am looking for a way to leave the connection open with mysql, not
> sending any queries, just waiting for mysql to notify me when a somthing
> changes.
>
> does mysql support that ?
> examples of doing that will be nice
>
>
> thanks,
> erez.
>
> _______________________________________________
> Linux-il mailing list
> Linux-il at cs.huji.ac.il
> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20131117/1de67c68/attachment.html>