This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-26
Channels
- # aatree (1)
- # admin-announcements (1)
- # beginners (84)
- # boot (239)
- # braid-chat (5)
- # braveandtrue (20)
- # cider (42)
- # cljsjs (4)
- # cljsrn (31)
- # clojars (18)
- # clojure (101)
- # clojure-austin (1)
- # clojure-gamedev (4)
- # clojure-madison (2)
- # clojure-poland (30)
- # clojure-russia (37)
- # clojurescript (95)
- # core-async (7)
- # cryogen (1)
- # css (3)
- # cursive (14)
- # datomic (8)
- # devcards (7)
- # dirac (2)
- # editors (2)
- # emacs (2)
- # funcool (1)
- # hoplon (15)
- # immutant (30)
- # ldnclj (37)
- # lein-figwheel (6)
- # leiningen (8)
- # luminus (5)
- # mount (1)
- # off-topic (59)
- # om (325)
- # om-next (7)
- # onyx (95)
- # parinfer (162)
- # proton (1)
- # re-frame (4)
- # reagent (23)
- # slack-help (4)
- # yada (43)
does someone have a gif of ?
@johnjelinek: you can get it in Chrome's dev tools, if you're using Slack through Chrome
https://emoji.slack-edge.com/T03RZGPFR/upside_down_parrot/62b7ebbc52e13655.gif
Agree or disagree: when you add or remove a business object from your system, you may create or drop some unknown number of tables from your RDBMS.
It depends. If the business object was synthesised from others, then no. If it was a primitive that was stored in the DB, then maybe.
You may also need the data to remain in the DB for accounting/auditing/reporting reasons.
I don’t mean a type of business object, I mean a record
say you have vehicle types, makes, and models
that’s a bad analogy hold on
OK how about music
Artists, Albums, Songs
when we add an Artist, we create tables for their albums and songs
and then when we delete an artist, we delete their tables and songs
you have “bon_jovi_albums” and “bon_jovi_songs"
and of course a table “artists” with “bon_jovi” in it
I’m 100% just bitching here BTW
now let’s say we add a new type of thing that artists can have, like “concerts” or “merch"
well, let’s just multiply out those tables!
one for each artist
or maybe not
because maybe some artists don’t have a lot of stuff
if they are “small” artists
so we have “small_artists_albums” and “small_artists_songs” tables
but maybe a concert doesn’t belong to an artist
so it belongs to the system
so those go in “system_concerts” where “system” is considered an artist
bah, I’m done I just need to buckle down and do this
oh and when we create IDs for songs and albums we need to bake the artist ID into it so we know which table it came from
right
that’s a thing
so the song Livin' on a Prayer might get an id in the database of “A342S1342_bon_jovi"
what if I told you that the only reason the schema is designed this way is because the DBA thinks that otherwise the tables might be too big and he doesn’t know how to set up partitioning?
@jcromartie heh, i have seen schemas like that, i suspect they are pretty common.
really?
where records of the same type are stored in various tables?
Good news and bad news: we won’t be using invisible ASCII character 29 to delimit different values crammed into the ID of certain records, but this was the plan at one point.
id fields are probably not where you should use invisible characters right?
gah, I really have to stop bitching about this architecture
I don’t know if this is a public channel archived somewhere on the internet for someone to find and get upset about
yeah- no kidding. couple of different reasons, in the old days, pre-widespread orm, lots of strange decisions arose out of the challenge of persisting object data with deep inheritance trees. more recently, have seen a few companies organized around independent teams moving with high velocity but all building a common application, naturally with a shared schema. the schema winds up being a kind of tragedy of the commons situation
i can see a dba, caught in the middle of a high velocity whirlwind, feeling the need to do what may be called pre-sharding 😉
http://cap.virginia.edu/sites/cap.virginia.edu/files/Webinar-flyerv2.pdf - wondering in the back of my mind if this would be good for fp someday.
@jcromartie: I just found an archive of this slack today, but I'm not sure it's supposed to exist
nice, as if “leiningen” weren’t hard enough to spell
oops, wrong window
Trying to start a new BASIC program, are we?
@borkdude: (belatedly) Python together with iPython is really nice for doing interactive shell stuff. https://ipython.org/ipython-doc/3/interactive/shell.html
There's also Plumbum, which I haven't used: https://plumbum.readthedocs.org/en/latest/
@echristopherson, "the people who harvest the flowers.” Nice