In my opinion (and I'm the one who suggested it) it is very rare that it
would be necessary.
I think that means that it *probably* won't help anything, but it
*definitely* won't hurt anything. So it may be a matter of taste.
Elan Ruusamäe wrote:
> but, should the template cache be flushed after upgrade or not?
> On Monday 14 March 2005 07:54, Bryan Alsdorf wrote:
>>Actually there was a bug that I fixed when merging the changes with
>>adding the estimated dev time and percent complete to the issue page. I
>>forgot to mention this in the change log.
>>Jeffrey D. Wheelhouse wrote:
>>>Joao Prado Maia wrote:
>>>>That's kind of strange, as the drop-down list should post an empty value
>>>>on the case of not selecting any options. Are you not seeing the
>>>>"Assignments" field on the update form?
>>>Ok, I tracked this back to what appears to be a stale compiled template.
>>> My system compiled the old template after the timestamp on your new
>>>version, and so apparently didn't redo it when I updated to 1.5.1.
>>>So false alarm I guess, but maybe "flush the template cache" could go
>>>into the general upgrade procedure.
>>>Thanks and sorry for the confusion!
>>Bryan Alsdorf, Software Engineer
>>MySQL AB, www.mysql.com
>>Are you MySQL certified? www.mysql.com/certification