It should be pretty hard to make a query fail beside the issues currently opened.
1,287 karma · joined October 2, 2012
It should be pretty hard to make a query fail beside the issues currently opened.
If you have a library that will return non operational error, just remove it from your project. If your code throws when it is not expected to, fix it.
This is like saying put a `try/catch(ignore)` everywhere. Seriously.
That being said, some websites don't play well...
I personally have removed their certificates from my system. This is the responsible move to do if you care about your security or don't want your computers to be used as part of the DDoS like we've seen against GitHub.
- changefeeds if you want to push data to your clients
- joins (if you are on a system without them - like Mongo)
- human-readable query language (if you are using SQL)Because of the chainable query language you don't have to build a new abstractions. You can just use the same.
Meaning that there is nothing (or very little) to learn yp switch from the driver to thinky.
The trend to go back to SQL databases now is fueled by the "same" poor reasons why people were going for NoSQL databases. You can't have everything...
Swiftype is the kind of product that you install once and then forget it because it just keeps working as you would expect. It's basically a good one :)
Did you just use Twitter stream API with track?
One of the websocket fails though: WebSocket connection to 'ws://nearby-cabs.param.xyz/socket.io/?EIO=3&transport=websocket&sid=E00UJLl1JkxBXlhmAAAG' failed: Error during WebSocket handshake: Unexpected response code: 400
This is definitely the most ironic part.
It also doesn't take years to get a H1-B...
I wouldn't really call it taste though but that's another debate.
- Are blue treemap your only value CBinsights? Well if you felt like you had to write about it, so maybe...
- Also public shaming using "Y Combinator company" instead of naming the company is shameful. Don't lump together all the YC companies for your own greed of getting attention.
- Your TOS blows. Close their account and send them a mail if you didn't want them to use your product.
In this case, you can do r.table("data").get(1) // get the current version of the document with id 1 r.table("history").getAll(1, {index: "id"}) // get all the previous versions of the document with id 1. And you can order them by `last_updated` if you want too.