3 ms·
> Yes, or you can skip that part and do the tricky part in an actual programming language Are you proposing pulling in an entire dataset into memory and post-p
by tdurden 8y ago
> Yes, or you can skip that part and do the tricky part in an actual programming language
Are you proposing pulling in an entire dataset into memory and post-processing it vs. creating efficient SQL to get what you need?
- blablabla123 8y agoAs crazy as this sounds, yes. Not the entire dataset of course, a selection of it and then tie things together on the fly. I've seen a handful of systems (one of them I wrote myself :D) that did complex queries. In part and in certain situations this can be very efficient, no doubt. But what I observed is: - dev-wise these systems become one-man-shows - implementing feature over feature becomes exponentially slower with time - initial performance is there but it turns into slow performance over time I prefer to do things on the application side.
- sitkack 8y agoSounds like you could benefit from learning SQL.
- orf 8y agoJust so you are aware, in reality all the points you listed are exactly the results of what you are describing. It becomes a one man show because anyone competent is going to run away from that mess right away. New features become exponentially slower with time because you are re-implementing some ad-hoc SQL implementation in JavaScript of all things. Initial performance is fine on your device setup, but drastically slows down over time when you pull in more data and do more complex things. As someone else pointed out, you could benefit from actually learning SQL. There is a reason it's used.