Ben Green
Ben Green
Hey Slava, Not sure what you mean by "the computation." Thinking about it now though, if triggers were abandoned for only reading from the write-ahead log, there would have to...
Oh okay. Yeah that would need to take place in the app server or a custom postgres extension that uses a Background Worker. As far as I know, there's no...
It's probably easier to use Docker. I've done this with multiple MySQL versions in this repository: https://github.com/nevill/zongji/blob/master/.travis.yml
Works fine for me. I have also just now updated the example to use the latest version of this package, 1.0.3.
_index is the row number in the result set, starting with 1 On Oct 19, 2015 6:34 PM, "jbaxleyiii" [email protected] wrote: > @numtel https://github.com/numtel can you go into more details...
Interesting. Are you going to update the test cases? It looks like you are now able to use a minimongo collection on the client? I've started a fork of pg-live-select...
There should be no problem with having the binlog in a different location. Make a pull request with the comment if you would like.
Right now there's no way to know without a full database. It could be looked up from a full node or block explorer. The protocol upgrade to state blocks goes...
Why do you have the `serverId` setting commented out? Each worker needs to have a unique value for `serverId`.
Not against this idea but not sure that this implementation is the best. It would be nice to not have the extra arguments contain a string value. Perhaps 2 boolean...