This would still allow for all of the dates to be joined to every view, while limiting which fields are shown in the explore so as to avoid duplication.
If you decide to go this route, the best practice would be to create a set that contains all of the fields that you want to bring through.
but I need to specify this join for multiple tables!
"why don't you just use from," I can hear you saying--I tried that, but then the dimension again shows up as a separate field for each thing I'm joining it to, defeating the purpose! EDIT: I thought about just generating the product of the cms ids and the dates, but in a world with 50k content items and 1000 dates, that ends up with a table of 50 million rows and I don't want that EDIT 2: I ended up implementing the cartesian-product-of-ids-and-dates idea, which from a query standpoint works really well.
So right now, in my explore there are 2 date dimensions and you need to know coming in which dimension to use depending on which table you're working with!
What's the right way to model this, so that I can select date in one spot in my explore and have it do the right thing on both of these tables, without creating a dates dimension table? I think I understand, but just to clarify: Are you trying to get the dates in both tables to work as a single unit?
If you're using Redshift, please note that this function is deprecated and could be completely withdrawn at some point.
By generating the series, and using the combination of the parameters, we could choose which fields we want to include in the join.
This could then be applied to each joins' About This Block A simple funnel is a great way to look at events or transactions.
Starting with just a few events, you can quickly get a sense of how users traverse your site or application.
It sounds like maybe you're looking to ensure that when someone filters on one of these dates, it will apply to both.Tags: Adult Dating, affair dating, sex dating