Lammertyn Pieter-Jan

Problem starts to occur in version 0.2.2a5

@wangxiaoying thanks for looking into this I agree that in most cases large query results will be used. But in some corner cases, you want to do a lot of...

Still seems to occur in version 0.2.4a3 

@dovahcrow I know, Virtual Memory Size (VMS) doesn't say much (I was just playing around to make the memory consumption human readable), but it can give an indication of how...

No same result:  Now the generated query is: ```sql --HINT DISTRIBUTE_ON_KEY(stratum_1) -- generating date key sequences in a cross-dialect compatible fashion CREATE TABLE omop_work_zidder.tmpach_117 AS WITH century as (select...

A good example of the 117 query for BigQuery is: ```sql WITH cte_date_range AS ( SELECT GENERATE_DATE_ARRAY(DATE_TRUNC(op1.observation_period_start_date, MONTH), DATE_TRUNC(op1.observation_period_end_date, MONTH), INTERVAL 1 MONTH) AS date_range, op1.person_id FROM omop_zidder.observation_period op1 ),...

And even better is checking that the observation_period_end_date is not in the future (observation_period_end_date is a required field, if it is not yet known, this date will probably be far...

Adding the check for end_dates not in the future does the trick (the query stays in the resource limits): ```sql --HINT DISTRIBUTE_ON_KEY(stratum_1) -- generating date key sequences in a cross-dialect...

ex: https://github.com/OHDSI/CommonDataModel/blob/v5.4.1/inst/csv/OMOP_CDMv5.4_Field_Level.csv?plain=1#L218

cfr https://github.com/OHDSI/CommonDataModel/issues/707 and https://github.com/OHDSI/CommonDataModel/issues/539