do things like parallel writes/concurrency you REALLY
>>> should use databases. That's what they were invented for decades ago.
>>> Nowadays there a bigger choice than ever: Relational or non-relational
>>> (NOSQL), single host or distributed, web interface or not,
system semaphores. Or just use a separate file for
> each worker.
>
> On Monday, October 10, 2016 at 11:09:39 AM UTC-4, Zachary Roth wrote:
>>
>> Hi, everyone,
>>
>> I'm trying to save to a single file from multiple worker processes, but
>> don'
Hi, everyone,
I'm trying to save to a single file from multiple worker processes, but
don't know of a nice way to coordinate this. When I don't coordinate,
saving works fine much of the time. But I sometimes get errors with
reading/writing of files, which I'm assuming is happening because mul
Wonderful. Running `Pkg.update()` did indeed do the trick (even for the
original data set that I had tried to load). Thanks so much for fixing
this. It's really great that a problem like this can be addressed so
quickly after one simple post; it's certainly a breath of fresh air after
workin
I'm having some trouble loading saved data, and I haven't had any luck in
looking for solutions online. I've reduced the code to as short of an
example as I could:
using HDF5, JLD
type Test
values::Vector{Integer}
end
x = Test([])
@save "test.jld" x
@load "test.jld" x
When I run the abov
I looked around a bit, and it seems that there is some plan to attach
return types to methods. Ideally, it would be nice if this information
could eventually be used to determine the type in question without having
to explicitly specify it; but it also seems that doing this could be
problemati