Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
John Sullivan
@sullivan-
hi, wow, welcome to longevity gitter!
you better mention me @sullivan- like that i guess or i will probably miss you
John Sullivan
@sullivan-
OMG work on SQLite back end is going so fast
all the model tests are passing!
John Sullivan
@sullivan-
I'm going to type a dot here every day i come here and nothing's happened
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
John Sullivan
@sullivan-
.
Mardo Del Cid
@mardo

Hey everyone!

I'm considering using the longevity framework, it looks so awesome! A couple of current concerns I have:

  • How to aggregate data? Is there native way of doing this on longevity or should I do queries directly to the db (let's say mongo) when I want to do groupBys, counts, avgs, and so on?
  • Is saving binaries (photos, docs, etc...) supported? or again, I need to talk directly to mongo's gridfs, for instance, to accomplish this?

Any help is much appreciated! :)

@sullivan- Great work so far, man!
John Sullivan
@sullivan-
Hi @mardo! I'm sorry I only got to seeing your message now. There is so little traffic here that I end up not checking in nearly often enough
Thanks for your support! Let me see if I can answer both of your questions in turn. The short answer is, both are possible and great ideas, but would take some effort to implement.
John Sullivan
@sullivan-
For aggregations, yes, you can always perform these directly against the DB. We can definitely add this as a longevity feature. It would take some work but it would be worth it. I am currently planning on doing an infrastructure refactoring, replacing a lot of home-grown reflection based code with the equivalent in shapeless. It would probably be best to hold off on implementing this feature until after this migration. With any luck, we'll get there before summer. In any event, I created a GitHub issue to track this excellent idea longevityframework/longevity#9
John Sullivan
@sullivan-
Support for binary data is another great idea. Probably a bit easier to implement than the the aggregates. Here's a ticket: longevityframework/longevity#10
I wish I could start implementing both of these today, but I've got a lot of high priority tickets on my stack right now. If you have any interest in contributing, I would happy to help you along however I could.
Mardo Del Cid
@mardo
Thanks for your valuable responses, @sullivan- ! One more question: Do you know any success stories using longevity? Any companies using it on production? This is not a show stopper for me, but still curious to know :)
John Sullivan
@sullivan-
@mardo I get so little feedback from users, it is frustrating. Makes me think it might have been better to not make my user manual so comprehensive, then at least I would get some usage questions :smile:
My suspicion is there are not many people using it in production at the moment. Schema migrations support is a fairly critical missing feature (https://www.pivotaltracker.com/story/show/108380704)
This time I got an email notification when you posted here, so next time I won't be three weeks late in responding :smile:
I wish I had a more optimistic response. Despite all the great features that longevity has, there are some good reasons I haven't hit 1.0 yet
John Sullivan
@sullivan-
The schema migrations thing is really high priority for me. But migrating the codebase to shapeless has become a sort of prereq for that, since it potentially affects the migrations implementation in significant ways