On Wednesday, August 31, 2016 at 9:47:52 PM UTC-7, Trevor Turk wrote:
>
> Hello,
>
> I've been reading about paged_each and it seems to work well in my
> testing, but I'm concerned about using it in production because the
> documentation says it uses a transaction internally.
>
> I plan to make
Hello,
I've been reading about paged_each and it seems to work well in my testing,
but I'm concerned about using it in production because the documentation
says it uses a transaction internally.
I plan to make a "backfill" script that iterates over all rows in a
production database and enqueu
On Wednesday, August 31, 2016 at 7:50:48 AM UTC-7, David Espada wrote:
>
> 2016-08-31 16:00 GMT+02:00 Jeremy Evans :
>
>> I suppose that is something I would consider as an addition to
>> delay_add_association. Do you want to work on a pull request for it?
>>
>> I have seen lightly the code and..
2016-08-31 16:00 GMT+02:00 Jeremy Evans :
> I suppose that is something I would consider as an addition to
> delay_add_association. Do you want to work on a pull request for it?
>
> I have seen lightly the code and... it frightens me a little, but can try
it :)
What I wish is having changed beha
On Wednesday, August 31, 2016 at 4:36:40 AM UTC-7, David Espada wrote:
>
> Hi all.
>
> There is a good little Sequel plugin called "delay_add_association" that
> avoids persistence when adding a child (one_to_many) to an entity. That is
> good in my
> system, because I like to have a consistent o
Hi all.
There is a good little Sequel plugin called "delay_add_association" that
avoids persistence when adding a child (one_to_many) to an entity. That is
good in my
system, because I like to have a consistent object representation without
persisting nothing until the end of the work cycle.
But