[4.x] Invalidate Stache status index value on date

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317

[jasonvarga]

Replaces #5089
Closes#2217

This is more of the direction I had in mind. This will save the status along with a timestamp of when the value should "expire". When loading the index, it'll loop over them, see if any timestamps are expired, then update them.

This obviously only solves the problem for the Stache. For Eloquent, we'd need to think of a different solution.
I still think the real solution is to scrap querying by status and instead put the logic in the query itself. (e.g. where date is in past, and published is true, etc). But that's a bigger job and likely a breaking change.

This should solve what @aerni needed (scheduled entries), and what @buffalom brought up (expired entries).

Todo:

• Tests are failing, so clearly it's not right. Figure that out. 😄
• Maybe add tracking of when last update was, to prevent the loop-on-load happening on every request. i.e. maybe throttle them to every 5 minutes, configurable.

[mmodler]

In our big project, we use this as hacky workaround
->where('status', '<>', 'draft')

So i would very much celebrate progress on this issue :)

[jasonvarga]

Fairly confident this won't be necessary after #9317