Raphaël Valyi
Raphaël Valyi
Actually, it's just better to simply make a search for ids rather than a huge read in those cases, so deferring that change until it gets more mindshare.
I propose we end implement the find_each API from active_record/relation/batches.rb for that.
done for m2o with the lazy property
for o2m associations, an idea could be that in relation.rb, in method_missing, when we have the method, of an Array (:each), with a Proc passed, then we could may be...
actually, it's probably where CollectionProxy should start kicking'in when we create one for the x2m associations
Double check the values OOOR is trying to send, probably there is some "nil" value which is not allowed in XML/RPC
may be more complex than what I said, for instance with p project having o2m tasks, with ActiveRecord we have: p.association_cache[:tasks].reflection => #[], :autosave=>true}, @active_record=Project(id: integer, name: string, created_at: datetime,...
Hello all, PR's are welcome. I'm the original author of the gem. However we have currently no very active project using it (Sadly our biggest Brazilian customer using it bankrupted...
An other possibility would be https://github.com/byroot/parsr not a lot of activity but the the guy seems to be doing very serious stuff at Shopify, so will probably do the job.
Hello, we should update OOOREST to last OOOR versions, this is an OOOREST bug.