Support for limit(), startsAt(), and endsAt() about emberfire

[aputinski]

@gpbmike I started hacking on this a while ago, unfortunately I just haven't had time to work on it. Hopefully I can add this feature in soon.

[gpbmike]

@aputinski no worries, thanks for you work. 👍

[outaTiME]

👍

[aputinski]

#63

[aputinski]

#83

[brandensilva]

👍

[gpbmike]

I think this is actually pretty straight forward and I have it working with the project I'm working on, except for one part that I could use some help on.

When a child is removed from the resulting Query, I don't know if it has been removed because another child was added and the removed child was pushed off the query, or if it was removed on the Firebase end and the query is now reflecting that. The difference would be if I want to update the store or not.

[jayphelps]

Status? This is blocking my team from considering Firebase.

[gpbmike]

@jayphelps this is my implementation with the aforementioned child_removed caveat: https://github.com/webhook/webhook-cms/blob/173ba55402eac39b07aa7873081f300e888337c5/app/adapters/application.js

[startupandrew]

@jayphelps -- if you want to know if the data is still there, just attached a "value" callback to the specific location where the data lives, and if it's null you'll know the data has been deleted.

[Zuur]

@gpbmike Thanks very much for sharing your solution; I'm just starting with schema design and the availability of priorities will affect the implementation of a few things - even if limit() is problematic at the moment it's enough to get me off the ground.

If you are able to implement the limit fix as @jayphelps suggests, or have any other updates here please post back again!

[jayphelps]

@aputinski did you have a solution to the child_removed issue described above (also shown here)?

[Zuur]

Oh, just realised that @gpbmike code does not have support for priorities, and in fact this issue does not mention priorities in the title either so does not really replace issue #63 which was closed above.

By my thinking, priorities, startAt and endAt offer significant functionality as a feature set and will impact the way a database(/firebase) is structured to begin with, where as limit() as a tool for processing data in batches (mainly pagination - which is not so much of a priority as things that affect a project's initial data schema).

Does anyone have any information on how to go about setting priorities currently? Can this issue be updated to include priorities as well so that that requirement isn't lost?

Edit as per jayphelps's comment below

[jayphelps]

@Zuur I think you mean @gpbmike? I haven't posted any code.

[oskarrough]

Any news on this?

[brunolemos]

+1

[Zuur]

+2

[brunolemos]

@gpbmike could you help us implementing Priority support in your code?
It would help us a lot. Thanks.

I found this other solution, but haven't tried it yet: https://github.com/rlivsey/fireplace

[Ghostavio]

+3

[ivohanke]

strange, this is quiet essential... any news??

[mwils]

+4

[brunolemos]

-1, not using firebase anymore. #meteor

[gpbmike]

For those of you still waiting on official support, this is what I've been using for a while now.

https://github.com/webhook/webhook-cms/blob/master/app/adapters/application.js

Feedback welcome of course.

[sararob]

@gpbmike we definitely want to add this. Thanks for putting something together. Firebase has added new querying functionality (see https://www.firebase.com/docs/web/guide/retrieving-data.html#section-queries), and we're going to be working on adding query support in the coming weeks.

[gpbmike]

The adapter extension I posted above supports some of the new querying functionality.

• orderBy
• limitToFirst
• limitToLast
• startAt
• endAt

[JarrodCTaylor]

The ability to query for specific data seems to be basic fundamental functionality of working with any database. In addition to the list above equalTo is also crucial to use emberfire in a serious manner.

👍 +1

[bttf]

@gpbmike thanks for your solution. I am able to query FB. I was also able to implement equalTo by adding just a few lines; fairly easy. Thanks again.

[wheredoesyourmindgo]

+1

[Emerson]

Waiting on this as well - hard to go beyond the hello world use case without proper query support

[jayphelps]

@Emerson and others, check out #169

[brendanoh]

I love the serverless pattern and Firebase Hosting is great but without the ability to really send queries I dont see how anyone could build anything substantial using EmberFire.

Let's assume I have an App that needs to do more that just Select by ID and Select All

How do you use this library if you cannot query Firebase?
Is there a way to pass native queries in via the data adapter?

Lets assume I have a user and I want to show all of his Posts but the Firebase repository has more than just his posts stored there. I cannot figure out how to pass in a query param (user = 5) to make that work in a normal way. There doesn't seem to be a way to Sideload either. One thing I can do is if the user has an array of Post Ids in their user model then I can iterate over them and make dozens of API calls into Firebase to get each post but that seems awful.

@katowulf thinks this is "not particularly challenging" but I cannot find any examples and I do not want invent the wheel. How do I 'drop to the Firebase API and use it directly' as I do not see examples, patterns or best practices.

In need of support / guidance / info.

Brendan

[dustinbrownman]

@gpbmike This looks great! I'm curious what version of firebase you're using. I get the undefined is not a function error whenever I try to call a querying method on ref (so ref.limitToLast(n) blows up).

[gpbmike]

@dustinbrownman you need to be using version 2.

[tstirrat]

landed in EmberFire 1.4.0+