as far as we're all on the same page, my job is done :P
On Saturday, February 6, 2016 at 3:17:46 AM UTC+1, Dave S wrote:
>
> On Friday, February 5, 2016 at 3:38:17 PM UTC-8, Dave S wrote:
>>
>> [...] The conditional queuing is something that I had already gone ahead
>> with, putting it in the mod
On Friday, February 5, 2016 at 3:38:17 PM UTC-8, Dave S wrote:
>
> [...] The conditional queuing is something that I had already gone ahead
> with, putting it in the model (outside the task function, so at the "top"
> level), and that seems to be working, too.
>
>
modulo a limitby() :-p
/dps
On Friday, February 5, 2016 at 3:38:17 PM UTC-8, Dave S wrote:
>
> On Friday, February 5, 2016 at 1:23:32 AM UTC-8, Niphlod wrote:
>>
>> you're translating my "like" as in "exactly". and making assumptions,
>> wrong ones.
>>
>
> I'm not sure I'm straying that far. Your further explanation, belo
On Friday, February 5, 2016 at 1:23:32 AM UTC-8, Niphlod wrote:
>
> you're translating my "like" as in "exactly". and making assumptions,
> wrong ones.
>
I'm not sure I'm straying that far. Your further explanation, below, I
think describes my current understanding.
What I was missing in my co
you're translating my "like" as in "exactly". and making assumptions, wrong
ones.
I just said that the environment in which the scheduler executes your task
is LIKE a shell one, where you launch the FUNCTION you queued, and then
exit the shell.
At the very "raw" structure of the scheduler, it
On Wednesday, February 3, 2016 at 1:10:37 AM UTC-8, Niphlod wrote:
>
> it's like you execute a task in a request coming from a new user every
> time. if you need to persist something, use a record in the db.
>
I'm catching on to that.
Trying to queue a task from a shell doesn't seem useful. T
it's like you execute a task in a request coming from a new user every
time. if you need to persist something, use a record in the db.
On Wednesday, February 3, 2016 at 7:24:07 AM UTC+1, Dave S wrote:
>
>
>
> On Sunday, January 31, 2016 at 4:13:07 AM UTC-8, Niphlod wrote:
>>
>>
>>
>> On Sunday, J
On Sunday, January 31, 2016 at 4:13:07 AM UTC-8, Niphlod wrote:
>
>
>
> On Sunday, January 31, 2016 at 7:12:41 AM UTC+1, Dave S wrote:
>>
>>
>>
>> On Saturday, January 30, 2016 at 8:50:32 PM UTC-8, Niphlod wrote:
>>>
>>> scheduler_run is the only way to keep track of executions.
>>>
>>
>> And the
On Sunday, January 31, 2016 at 7:12:41 AM UTC+1, Dave S wrote:
>
>
>
> On Saturday, January 30, 2016 at 8:50:32 PM UTC-8, Niphlod wrote:
>>
>> scheduler_run is the only way to keep track of executions.
>>
>
> And there is no session to carry a value over in, is there?
>
sorry, what ?
>
>
>>
On Saturday, January 30, 2016 at 8:50:32 PM UTC-8, Niphlod wrote:
>
> scheduler_run is the only way to keep track of executions.
>
And there is no session to carry a value over in, is there?
> BTW, in my experience, changing models doesn't need a restart.
>
>
That's what I was expecting, but
scheduler_run is the only way to keep track of executions. BTW, in my
experience, changing models doesn't need a restart.
On Saturday, January 30, 2016 at 10:31:40 PM UTC+1, Dave S wrote:
>
> I've finally done a scheduled task (and not for the project I thought I
> was going to). In the current
11 matches
Mail list logo
