Robert Kopaczewski
Robert Kopaczewski
Made a quick fix. Actually, it is not wsbench that is at fault, but optparse.js library. https://gist.github.com/1619157 Here you can get patch to apply. What I did? Updated lib/optparse.js to...
Silly me. make wasn't installed. Feel free to close, although it should output some errors, not just silently fail. I guess others had more or less same situation.
Thanks, that solves this for me. Seems though like @xando is having a different issue.
@Idered We do not have `OR` in core (and we probably won't add it any time soon) so I think the only way to do it is to make two...
Maybe use https://github.com/jhurliman/node-rate-limiter/ or https://www.npmjs.com/package/request-rate-limiter ? Or some custom lighter solution?
Current state of core: ``` all_types = {'string', 'text', 'integer', 'float', 'boolean', 'datetime', 'file', 'reference', 'object', 'array', 'geopoint', 'relation'} noindex_types = {'text', 'file', 'object'} # these cannot have any indexes...
text, file and object cannot have any index at all - be that order, filter or unique. So text, file, object, array, geopoint and relation all cannot be unique.
@Idered you mean update multiple objects? If so - nope. 1 request updates only 1 object.
It’s the same as with any update in REST - they are meant to update 1 object at a time. But if you update by id - you can update...
We can do this but this would make current process more complex as it would require additional step for root domains - when CNAME is flattened, we would require TXT...