I'm glad to see this thread. I've been mulling over this exact issue of deleted_at code leakage with a naive soft-delete implementation. My immediate thought was to use views, so its nice to see this is not yet another…
Yes, unfortunately I was in that case where pagination simply wasn't provided by the feed. Push notifications of course wouldn't have worked (if they were even supported, and I don't believe they were), since otherwise…
The one time I wanted to use an RSS feed I found I had no (acceptable) way to ensure I didn't miss data. New items could be truncated off the feed after anywhere between 10 minutes and two hours, and the solution to…
I've found in my own use of rust I want async/nonblocking for two things. 1. Be able to timeout a read of a socket 2. Be able to select over multiple sockets, and read whichever is ready first Usually a combination of…
I'm glad to see this thread. I've been mulling over this exact issue of deleted_at code leakage with a naive soft-delete implementation. My immediate thought was to use views, so its nice to see this is not yet another…
Yes, unfortunately I was in that case where pagination simply wasn't provided by the feed. Push notifications of course wouldn't have worked (if they were even supported, and I don't believe they were), since otherwise…
The one time I wanted to use an RSS feed I found I had no (acceptable) way to ensure I didn't miss data. New items could be truncated off the feed after anywhere between 10 minutes and two hours, and the solution to…
I've found in my own use of rust I want async/nonblocking for two things. 1. Be able to timeout a read of a socket 2. Be able to select over multiple sockets, and read whichever is ready first Usually a combination of…