r/javascript • senior HTML9 engineer • Apr 22 '15

Meteor Postgres

http://www.meteorpostgres.com/
28 Upvotes

5 comments sorted by

0

u/[deleted] Apr 22 '15

[deleted]

4

u/pdiniz Apr 23 '15

That is referring to the initial data set that is sent to the client. Once that data set to the client it will remain reactive, but it will be constrained by the data limitations you put on it. Let's say you asked for the top 100 results. Upon loading the page you will get the first 100 results, but any new results added will also continue to be added to your set, and any changes (updates, deletes) will also continue to be made to you set. This was provided as an option if you were looking to limit the data provided to the client. You can still make all the data available to the client at all times if you choose to do so and that data will be entirely reactive as well.

1

u/ahref Apr 24 '15

is that any results added by the server and/or client.

For example say I subscribe to the last year's worth of orders on an administrative part of an eCommerce system.

If a user puts in a new order via server and/or client. The text implies in "Any further pagination and or data modification will have to be done client side." that the new order would be missing from the administrator's data set.

Thanks for clarifying! :D

1

u/pdiniz Apr 24 '15

Yes. This has been badly worded and we are fixing the docs. If you are subscribing to the last years worth of orders, and new orders are coming in they will continue to be sent over to the client as they update. What that means is that if you are subscribing to this years order and you decide you want last years, then that won't be reactive until you refresh the server. Its a limitation we are currently working on solving.

1

u/ahref Apr 25 '15

Awesome, Thanks for clarifying :D

0

u/ahref Apr 22 '15

That doesn't sound reactive or multi-user friendly at all.

Thanks for the headsup.