swift - Firebase snapshot.key not returning actual key? -


i have query searches user based on user id. 

usersref.queryorderedbychild("email").queryequaltovalue(email).observeeventtype(.value, withblock: { snapshot in     if snapshot.exists() {         print("user exists")         print(snapshot.key)

the query returns correct user, line print(snapshot.key) literally returns word "users", , not actual user id. print(snapshot) returns following user:

snap (users) {    delyncz9zmttbikfbnyxtbhuadd2 =     {        email = "test3@gmail.com";        "first_name" = test;        "last_name" = test;    };

how can delyncz9zmttbikfbnyxtbhuadd2? can email using let email = child.value["email"] can't key because it's not named attribute.

thanks!!

edit: updated code frank's answer. getting ambiguous use of key

query.observeeventtype(.value, withblock: { snapshot in             print(snapshot.key)              if snapshot.exists() {                 print("user exists")                  child in snapshot.children {                     print(child.key)

when run query @ location, result list of matching children. if there single matching item, result list of 1 child.

you're printing key of resulting children. since there no single result, sdk prints key of location/collection queried: users.

what you're looking loop on matching children , print keys:

let query = usersref.queryorderedbychild("email").queryequaltovalue(email) query.observeeventtype(.value, withblock: { snapshot in     child in snapshot.children {         print(child.key)     } })

-

Popular posts from this blog

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

i working apache nifi 0.5.1 on groovy script replace incoming json values ones contained in mapping file. mapping file looks (it simple .txt): header1;header2;header3 a;some text;a2 i have started following: import groovy.json.jsonbuilder import groovy.json.jsonslurper import java.nio.charset.standardcharsets def flowfile = session.get(); if (flowfile == null) { return; } flowfile = session.write(flowfile, { inputstream, outputstream -> def content = """ { "field1": "a" "field2": "a", "field3": "a" }""" def slurped = new jsonslurper().parsetext(content) def builder = new jsonbuilder(slurped) builder.content.field1 = "a" builder.content.field2 = "some text" builder.content.field3 = "a2" outputstream.write(builder.toprettystring().ge...
Read more

node.js - How do I prevent MongoDB replica set from querying the primary? -

read-operations-only: is there way have mongodb replica set, make mongodb instance on box connected to, mongodb gets queried? i have 3 ec2 instances behind aws load balancer. on each ec2 instance runs mongodb, part of replica set. i have express endpoints on nodejs , connect replica set follows mongodb.mongoclient.connect('mongodb://1.1.1.1,2.2.2.2,3.3.3.3.', function (err, db) { if (err) { complete('{}'); } else { i distribute load of queries evenly across 3 instances of mongodb replica set instead of default having queries routed ec2 instance primary mongodb defined, because destroys point of load balancer (which balance load of queries across 3 instances evenly). my understanding when connecting mongodb replica set, primary instance selected unless primary instance down, , therefore purpose of every secondary instance serve backup. in example people call hot,cold,cold. because there 2...
Read more