You could create another table in the database that would hold the last write times of these tables. Create a separate table with the columns "table name" and "mod date", then create or modify the wrapper which you use to write information to the RT tables to, before they write to the appropriate real time table, update the time in the mod access time for that table to the current time. Then, when a call comes in, check that table entry and see if it needs to be reloaded.
<br><br>I don't know if that makes this a good idea, but it seems possible.<br><br><div><span class="gmail_quote">On 3/27/07, <b class="gmail_sendername">Tilghman Lesher</b> <<a href="mailto:tilghman@mail.jeffandtilghman.com">
tilghman@mail.jeffandtilghman.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Tuesday 27 March 2007 16:06, Luigi Rizzo wrote:
<br>> Googling a bit, it seems that you can get the modification date of<br>> a database table with a "SHOW TABLE STATUS" query, and this would<br>> at least help to know if the cache is in sync.<br><br>
That does not appear to be portable. Postgres, for example, has no such<br>command.<br><br>--<br>Tilghman<br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">
Easynews.com</a> --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a>
<br></blockquote></div><br>