<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Yeechang Lee wrote:
<blockquote cite="mid:17975.5624.355926.615137@dobie.ylee.org"
type="cite">
<pre wrap="">Bruce Markey <a class="moz-txt-link-rfc2396E" href="mailto:bjm@lvcm.com"><bjm@lvcm.com></a> says:
</pre>
<blockquote type="cite">
<pre wrap="">There is no limit within myth so items could be placed in
the 'program' table months or years in advance.
</pre>
</blockquote>
<pre wrap=""><!---->
There is one limit I know of. One way I can trigger by the following:
Schedule Recordings|Search Lists|Movies
The resulting list abruptly ends after about 1000 entries, which for
me covers the next 27 hours' worth or so of listings. This is, I
presume, a limit within mythfrontend (And one I'd like to change;
where should I look in the code?); within MythWeb,
Searches|Movies
will, after about 60 seconds of churning, properly bring up all movie
listings over the next two weeks. (Note that php_value memory_limit in
mythweb/.htaccess must first be raised to some ginormous figure from
the stock 32M; on my box 256M works.) The HTML is an impressive 14M in
size.
</pre>
</blockquote>
Thanks Bruce and Yeechang for the information. <br>
<br>
I was mainly concerned with the abilities of mythfilldatabase--can it
handle importing data that's more than 2 weeks away. It sounds like the
main limitation is with the total amount of information, rather than
the length of time. Since I'm only dealing with about 10 'channels' I
think I'll try lengthening the time period and see what that does.<br>
<br>
Jon<br>
</body>
</html>