This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-24
Channels
- # admin-announcements (16)
- # announcements (2)
- # beginners (12)
- # boot (92)
- # cider (1)
- # clojure (149)
- # clojure-argentina (1)
- # clojure-australia (3)
- # clojure-dev (2)
- # clojure-italy (2)
- # clojure-japan (1)
- # clojure-russia (9)
- # clojurescript (48)
- # clojutre (2)
- # core-logic (18)
- # datomic (48)
- # editors (43)
- # emacs (11)
- # funcool (12)
- # hoplon (11)
- # ldnclj (30)
- # ldnproclodo (1)
- # rdf (6)
- # re-frame (13)
- # reagent (10)
- # testing (1)
- # yada (1)
@danielcompton: though if there is a better place to ask that question I am all ears. I think though I will stick with datomic for now.
Probably #C03S1KBA2 will get you more of a response
Postgres is the other alternative that has a lot of support and mindshare
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?
@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.