I love the Miltons GF frozen pizzas from Costco. Kirkland brand is meh imo
I love the Miltons GF frozen pizzas from Costco. Kirkland brand is meh imo
I definitely read your post the other way, but yeah, this way is bad too. I hadnβt noticed they donβt have a setting for it.
I will skip liking your upstream reply - solidarity!
Dopamine roulette
A meme showing two red buttons. One says βthey should make more musicβ and the other says βI wish it was more like their old stuffβ. A man is shown sweating over the choice of which button to push.
Adjacent
we are so back, etc.
RTβs voice was never my thing but I felt the exact same way the first time I heard the acoustic version of βPushβ - he was not just a guy trying to pump out radio plays.
inb4 the e/h2o bros show up
Totally understand this feeling π
Can confirm the recipe is AWESOME
Vasectomy humor aside: I know folks whoβve lost their only son or only daughter out of some number of the other, and I canβt imagine how much it would hurt to be asked this especially early on.
Lots of these situations desperately need some new quips.
Iβve got 4 boys and my standard was βwe did, 4 timesβ
Wish Iβd thought to add the vasectomy bit though - Intrusive question, meet over sharing!
Off topic but delighted to see aplomb in the wild
The business requirement/problem (consolidate multiple instances of a table) and the use of storage layer vs. SQL to do so. Iβve bumped into this twice with similarly implemented ERP systems, but maybe itβs just not that common otherwise? Thanks for engaging on it!
I feel like the corollary to this is everyone wants to believe theyβre Rick Rubin
The ext table presents the same result (plus some metadata) as if youβd unioned all the source tables.
I wasnβt very clear in my wording - this is multiple physical source tables (one per business entity). Iβm extracting each table to a separate file. All instances of a given table (entity1.customer, entity2.customer, etc) have the same columns, and Iβm exposing them all using one DW external table.
One or more file per entity, if that matters - N files per table.
I land them in a common data lake location and provide access using a view. Itβs effectively a union but at the file level instead of SQL.
Is there a name for this?
#dataBS I have a terminology question: Iβm extracting more than one instance of a table from a single source (e.g., ERP customers). Same source db, same table definition, different data as theyβre for separate entities.
1/2
Weβre not sure what else is in this one of ours but weβve loved having Pyrs!
Is that a Great Pyr? That expression is very familiar
<screams in COTS design decisions>
Proposal: alt tag #dataBSerious for when things get real
Absolutely not. Poast on.
Clearly time for an SR π
this is better
I probably missed that by a generation here in central CA
Having previously worked at an ag vertical company the novelty of this has worn off π