admin管理员组

文章数量:1278978

A similar question was asked here, but the one accepted answer doesn't really answer the question.

Using AngularFire, is it possible to to create relational-style databases? Or access the UniqueIDs?

When adding nested items to Firebase via AngularFire, each item is actually set under another index numbered numerically.

Because of this, I'll need to reference the user's products with the following relative url:

users/:id/products

My question is, once I have created a user (or anything for that matter), how do I get the index value?

// Get the users
var ref = new Firebase('')
var promise = angularFire(ref, $scope, 'users', {})
promise.then(function() {
  // Can I get the ID from here somehow?
})

// Users saves a product
id = null // ???
var product = {
   name: 'new product',
   desc: 'this is a new product'
}
var ref = new Firebase('/' + id + '/products')
var promise = angularFire(ref, $scope, 'products', {})
promise.then(function() {
  $scope.products.push(product)
})

Update

To clarify, this isn't a question about user authentication. I already have that taken care of. Sorry for the confusion.

I've just run into a brick wall when I start making things "under" other things in Firebase. Doesn't matter if it's users or giraffes.

If I make "Stores," each Store has "Products" (let's say.)

I'd like to be able to retrieve them with

stores/{storeId}/products

But the storeId would ideally be the index ID that is created from AngularFire (See the picture I have attached). The trouble is, AngularFire just creates this ID without letting me know about it.

If I had some success function like

success: function(response) { 
  $scope.store.id = response.indexId
}

That would make the most sense, but it doesn't appear AngularFire is prepare this very needed functionality. Prove me wrong, please. :)

A similar question was asked here, but the one accepted answer doesn't really answer the question.

Using AngularFire, is it possible to to create relational-style databases? Or access the UniqueIDs?

When adding nested items to Firebase via AngularFire, each item is actually set under another index numbered numerically.

Because of this, I'll need to reference the user's products with the following relative url:

users/:id/products

My question is, once I have created a user (or anything for that matter), how do I get the index value?

// Get the users
var ref = new Firebase('https://myapp.firebaseio./users')
var promise = angularFire(ref, $scope, 'users', {})
promise.then(function() {
  // Can I get the ID from here somehow?
})

// Users saves a product
id = null // ???
var product = {
   name: 'new product',
   desc: 'this is a new product'
}
var ref = new Firebase('https://myapp.firebaseio./users/' + id + '/products')
var promise = angularFire(ref, $scope, 'products', {})
promise.then(function() {
  $scope.products.push(product)
})

Update

To clarify, this isn't a question about user authentication. I already have that taken care of. Sorry for the confusion.

I've just run into a brick wall when I start making things "under" other things in Firebase. Doesn't matter if it's users or giraffes.

If I make "Stores," each Store has "Products" (let's say.)

I'd like to be able to retrieve them with

stores/{storeId}/products

But the storeId would ideally be the index ID that is created from AngularFire (See the picture I have attached). The trouble is, AngularFire just creates this ID without letting me know about it.

If I had some success function like

success: function(response) { 
  $scope.store.id = response.indexId
}

That would make the most sense, but it doesn't appear AngularFire is prepare this very needed functionality. Prove me wrong, please. :)

Share Improve this question edited May 23, 2017 at 12:01 CommunityBot 11 silver badge asked Oct 18, 2013 at 21:54 Adam GrantAdam Grant 13.1k10 gold badges60 silver badges65 bronze badges 6
  • fyi, the last argument of your angularFire() call, {}, is now deprecated. You can acplish a similar thing by doing $scope.users = {} before initing the angularFire. – bennlich Commented Oct 19, 2013 at 15:29
  • @bennlich am I wrong in thinking you will always get an object back no matter how you initialize before angularFire returns? And if so, isn't the suggestion that you can use .push() on an implicit angularFire binding in the docs inaccurate? I know this is slightly off-topic but I think still relevant. – hiattp Commented Oct 20, 2013 at 15:54
  • @hiattp Why would .push() be wrong? – Adam Grant Commented Oct 20, 2013 at 17:33
  • Well, JavaScript objects don't have a push method, just arrays. – hiattp Commented Oct 20, 2013 at 18:02
  • @hiattp See this fiddle: jsfiddle/4zGvz/2. You get an object back if it starts life as an object, and an array back if it starts life as an array. Otherwise it waits to see what kind of data already exists at the reference. – bennlich Commented Oct 21, 2013 at 3:37
 |  Show 1 more ment

3 Answers 3

Reset to default 4

There definitely seems to be a way to do everything you'll want. Your first question was:

var promise = angularFire(ref, $scope, 'users', {})
promise.then(function() {
  // Can I get the ID from here somehow?
})

Once the promise returns for this call, your $scope.users will be an object of users whose keys are the id values of the users you've created. So to access the ids of those users:

var promise = angularFire(ref, $scope, 'users')
promise.then(function() {
  for(var userId in $scope.users){
    console.log("User Id: " + userId);
  }
});

This doesn't seem tremendously helpful to what you are ultimately trying to achieve, but at least you can see how to return the ids for all users from AngularFire.

Since you want to create products under users I think @bennlich was trying to get at the fact that the user's id should be available from some other variable, like a user object if you are using angularFireAuth. But whenever you do have the id, there are multiple ways to create objects under that user. Give that you have the user's id, you'll have the following ref:

var userProductRef = new Firebase('https://myapp.firebaseio./users/' + userId + '/products');

So one way to create a product using AngularFire would be creating an explicit data binding with angularFireCollection:

$scope.userProducts = angularFireCollection(userProductRef);
// create a new product
var newProductRef = $scope.userProducts.add({name: 'new product', desc: 'this is a new product'});
console.log("New product id: " + newProductRef.name());

If you wanted to use the implicit data binding, you wouldn't need to use AngularFire directly for the object creation at all, as the data sync is "implied." In this case you have to keep in mind that AngularFire is just an extension/augmentation of the vanilla Firebase API, and is not intended to be a substitute. So you might have something like this, using the Firebase .push method to create the id:

// sync $scope.userProducts with Firebase
var promise = angularFire(userProductRef, $scope, 'userProducts');
// create a new product when promise fulfilled
promise.then(function(){
  var newProductId = userProductRef.push(); // here is your id
  // this will sync to Firebase automatically because of the implied angularFire binding
  $scope.userProducts[newProductId] = {name: 'new product', desc: 'this is a new product'};
});

These methods use AngularFire for object creation, but as mentioned I think it helps not to think of AngularFire as a replacement for the Firebase API, it just makes mon Angular use cases much easier. Depending on how your view and CRUD actions are structured, it may or may not make since to use AngularFire for Creation, even if it is useful for Read/Update/etc actions. And as a final note, while you can do this type of relational data structuring in Firebase using AngularFire, it's likely to cause difficulties later. You should strongly consider restructuring (de-normalizing) your data to optimize for Firebase's key/value store design.

In the new version of AngularFire, you can just iterate through the AngularFire object as though it were a normal javascript object.

$scope.users = {};
angularFire(ref, $scope, 'users').then(function() {
    for (var id in $scope.users) {
        if ($scope.users.hasOwnProperty(id) {
            ...
        }
    }
});

I don't think this is really what you want to do though, as you'd be loading all user data into every client. You should probably have the client provide a username or some other kind of id, maybe with Firebase Simple Login.

Finally, are you familiar with your browser's developer tools? They can be extremely useful for peeking inside of objects you don't know what to do with, like an AngularFire, to see how they're structured internally.

I have the best and quickest answer for all such kind of problems guys!!!

var chru;
    var ref = new Firebase("https://myapp.firebaseio./users/");
    var sync = $firebase(ref);
    var users= syncSelect.$asArray();
    $scope.users= users;
    users.$loaded().then(function() {
        chru = users.length;
    });

    $scope.specificIdOnSelect = function() {
        var jj;
        for (jj = 0; jj < chru; jj++) {
            var keyer = users.$keyAt(jj);
            var rec = users.$getRecord(keyer);

            if ($scope.userSelected== rec.name) {
                alert("Unique Key of " + $scope.users+ " is " + users.$keyAt(jj));
            }
        }
    };

    $scope.allIds = function() {
        var jj;
        for (jj = 0; jj < chru; jj++) {
            var keyer = users.$keyAt(jj);
            var rec = users.$getRecord(keyer);
            alert("Unique Key of " + $scope.users+ " is " + users.$keyAt(jj));
        }
    };

Try it and then please let me know if this helps!!!

本文标签: javascriptGet the index ID of an item in Firebase AngularFireStack Overflow