pg-live-select
pg-live-select copied to clipboard
numtel
Live Updating PostgreSQL SELECT statements
I have updated your benchmarking tool and added comparisons with other similar projects. See it [here](https://github.com/mitar/node-pg-reactivity-benchmark). Results are at the end. It seems your project works the best both memory-wise...
Is there any handling of broken feeds occurring? Looking through the code base, I'm having trouble spotting anything. Simple test: Bring up a DB, initialize a livequery successfully, bring down...
I'm having difficulty understanding the information being presented to me. Not sure if it's a bug, if it's happening in the wrong order, or if I'm just missing something completely....
Does the package support using schemas? ``` javascript // Instantiate LivePg class var liveDb = new LivePg(app.get('db_url') + '?ssl=true', 'myapp'); // Create a live select instance liveDb.select('SELECT * FROM connect.contact').on('update',...
Hi, I tried your documentation, but it failed and after checking I realized that your ``` javascript var liveDb = new LivePG('postgres://user:pass@host/db', 'myapp'); ``` should be ``` javascript var liveDb...
It looks like pg-live-select is currently working with manual triggers. This is a lot of work and hard to do right. Is the live-select functionality achievable with the Logical Decoding...
So...I looked more deeply into Lovefield's query observers. When a change occurs, all observed queries that depend on the table are re-executed then the rows added and removed are determined...
