/meta/ - Board Meta
[Make a Post]>>6718
Yes it should represent last reply. Here is an example code.
>SELECT MAX(Date) FROM Posts WHERE Board = <whatever board> AND Parent = <whatever thread>
Yes it should represent last reply. Here is an example code.
>SELECT MAX(Date) FROM Posts WHERE Board = <whatever board> AND Parent = <whatever thread>
>>6718
The idea of the L: date was so you could just scan through the list of dates and find the one closest to where you last left off, then open all the threads that come after it. Having it represent the date of last reply would mean you'd have to inspect each L: date individually. But yeah, I guess having it be tied to the last reply would make it more powerful, I'll change it when I get the chance to
The idea of the L: date was so you could just scan through the list of dates and find the one closest to where you last left off, then open all the threads that come after it. Having it represent the date of last reply would mean you'd have to inspect each L: date individually. But yeah, I guess having it be tied to the last reply would make it more powerful, I'll change it when I get the chance to
Actually nevermind, it takes about 40ms to perform the sql query in >>6719, and there's about 300 catalog items to generate including the overboard items. I'll keep it in mind if the catalog generation ever gets optimized
[Catalog][Overboard][Update]
[Reply]0 files, 4 replies
For example if that thread gets 100 more replies and stays active for many more months, the L: displayed will still be that of the 300th post made today, which is misleading (though technically true).
Suggestion: L: should represent last reply (sage or not), not last bump?