Why does this Firebase ".indexOn" not work? -


so have data so: 

pushnotifications {     -k - rwegd541pignoxxuh: {         message: "xiaoyu hugh hou bid @ $900 on task: new p..."         notifyid: "facebook:10100683829966199"         relatedtask: "-jzl8xkaxgcv19niochm"         timestamp: 1443594566599     } - k - rwpcblqa04vjt4bwm: {         message: "sam feldt bid @ $1100 on task: new post g..."         notifyid: "google:1043268349966197"         relatedtask: "-jzl8xkaxgcv19niochm"         timestamp: 1443594721963     } - k - rwum3 - 0 g0q9i96whg: {         message: "sam feldt bid @ $600 on task: no firebase..."         notifyid: "facebook:10100683829966199"         relatedtask: "-jztsk2tilo46ovqj1nn"         timestamp: 1443594741347     } }

in code, need latest notification below "notifyid". here code:

ref.child('pushnotifications')    .orderbychild("notifyid")    .limittolast(1)    .on("child_added", function (snapshot) {        console.log("found new notification...");        sendpush(snapshot.val());    });

in firebase security rule, have index rule: 

 "pushnotifications": {       ".read": "auth != null",       ".write": "auth != null",       "$pushid": {         ".indexon": ["notifyid", "timestamp"],       }     },

it index structure follow firebase docs here: docs

but when run code, console still log

firebase warning: using unspecified index. consider adding ".indexon": "notifyid" @ /pushnotifications security rules better performance

which not make sense since did already. please help!

you need put .indexon 1 level higher did:

 "pushnotifications": {     ".read": "auth != null",     ".write": "auth != null",     ".indexon": ["notifyid", "timestamp"] },

for comparison @ firebase documentation on indexes, uses json example:

"dinosaurs": {   "lambeosaurus": {     "height" : 2.1,     "length" : 12.5,     "weight": 5000   },   "stegosaurus": {     "height" : 4,     "length" : 9,     "weight" : 2500   } }

with indexing rule:

{   "rules": {     "dinosaurs": {       ".indexon": ["height", "length"]     }   } }

Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more