Fork me on GitHub
#re-frame
<
2015-08-24
>
sisawat06:08:36

@danielcompton: though if there is a better place to ask that question I am all ears. simple_smile I think though I will stick with datomic for now.

sisawat06:08:52

Thanks for your feedback as always

danielcompton06:08:55

Probably #C03S1KBA2 will get you more of a response

danielcompton06:08:28

Postgres is the other alternative that has a lot of support and mindshare

sisawat06:08:38

Well that's a good thing

sisawat06:08:53

Since I have a fair amount of experience there

sisawat06:08:40

And using a RoR REST API sitting on postgres was what led me to reframe initially

ulsa19:08:24

I want to keep track of selected rows in a (jQuery) table, and perform various operations (delete, import, schedule, etc) of all selected rows. Should I: a) track each select/deselect, dispatch add/remove events, and in handlers add/remove from collection in db, or: b) just toggle class "active" on click, and when dispatching operation event, get currently selected rows c) something else entirely?

ul19:08:07

@ulsa Personally I would prefer a) because it is more transparent and consistent. If you app-db structure designed carefully enough it should not take performance down.

ulsa20:08:52

@ul: Thx. Yeah, it feels cleaner somehow.

ul20:08:16

Actually I use this approach in current project even for large lists works fine. But, honestly speaking, not with reactive reactions/ratoms but with freactive.core ones plus caching subscriptions.

ul20:08:14

But I guess reactive also should play good.

ulsa20:08:24

Currently retrofitting re-frame into mishmash of callbacks, a bit tricky