From: Evan R. <eva...@gm...> - 2006-04-21 05:16:59
|
well, i never delete anything. so for me it's useful to have an idea when = i actually read something. and when it was cached is seperate data that shouldn't be tampered with. it's your basic principle of having an insert and update timestamp on the record. in the end it's not absolutely necessary, but the auto-timestamping on cache_time needs to go. i suspect that the adodb stuff adds it, when we ad= d the field, as it's the first timestamp in the table. i don't want the cache_time to be changed when i mark something read. (if we don't know whe= n it was marked read, then it's not a big problem right now) On 4/21/06, Kevin <ke...@dr...> wrote: > > > > hey guys, > > > > a side note i just remembered. > > > > in the feed items table, on my install, i've stripped out the > > auto-timestamping on the cache_time field...since this is actually > > changing > > valid data from the rss feed. in order to do it correctly, i'd add > > another > > field for date_changed or something, which is then updated when the use= r > > marks the item read (or whatever other action). > > > > any objections to me correcting that, or shall i just add it as a > > bug/feature request for the time-being? (if sourceforge wants to > work...i > > am getting only 500 errors tonight.) > > publish_time uses the timestamp from the rss feed. > cache_time is when it is inserted into the database. It is primarily use= d > for items deletes. We also display it in the view. > > Do we care when a user marks an item read? How is that useful? > > -- > Kevin > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmdlnk&kid=120709&bid&3057&dat=121642 > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel > |