Snowflake-SQL编译错误:缺少列规范

时间:2019-06-24 20:32:37

标签: snowflake

我有这个查询:

create table analytics.as_screenings_activity_stopped as (
select 
ka.vhost,
ka.SFDC_ACCOUNT_KEY, 
ka.count_units, 
min(d.go_live_date), 
s.RECORD_TYPE_NAME,
s.vplus_stage, 
s.screenings_enabled_date,
s.screenings_first_use_date,
sd.most_recent_screen_date,
case when sd.most_recent_screen_date >= dateadd(days, -90, current_date) then 'N' else 'Y' end as last_screen_90_or_more_days_ago

from analytics.key_account_yn as ka
    left join analytics.go_live_date as d on ka.SFDC_ACCOUNT_KEY = d.SFDC_ACCOUNT_KEY 
    left join analytics.screenings_enabled_first_use_date s on ka.SFDC_ACCOUNT_KEY = s.SFDC_ACCOUNT_KEY
    left join analytics.most_recent_screen_date sd on ka.vhost = sd.vhost 
where ka.key_account_yn = 'Y' and s.vplus_stage = 'Active'
group by 
ka.vhost,
ka.SFDC_ACCOUNT_KEY, 
ka.count_units, 
s.RECORD_TYPE_NAME,
s.vplus_stage, 
s.screenings_enabled_date,
s.screenings_first_use_date,
sd.most_recent_screen_date
order by ka.vhost);

当我不尝试创建表时,它运行得很好。我正在使用与其他查询相同的代码格式。我收到以下错误:

SQL compilation error: Missing column specification 

该如何解决? 谢谢, 艾丽莎

1 个答案:

答案 0 :(得分:0)

问题已解决-我需要为min(d.go_live_date)提供一个别名。感谢this的文章。

更新的查询:

create table analytics.as_screenings_activity_stopped as (
select 
ka.vhost,
ka.SFDC_ACCOUNT_KEY, 
ka.count_units, 
min(d.go_live_date) as go_live_date, 
s.RECORD_TYPE_NAME,
s.vplus_stage, 
s.screenings_enabled_date,
s.screenings_first_use_date,
sd.most_recent_screen_date,
case when sd.most_recent_screen_date >= dateadd(days, -90, current_date) then 'N' else 'Y' end as last_screen_90_or_more_days_ago

from analytics.key_account_yn as ka
    left join analytics.go_live_date as d on ka.SFDC_ACCOUNT_KEY = d.SFDC_ACCOUNT_KEY 
    left join analytics.screenings_enabled_first_use_date s on ka.SFDC_ACCOUNT_KEY = s.SFDC_ACCOUNT_KEY
    left join analytics.most_recent_screen_date sd on ka.vhost = sd.vhost 
where ka.key_account_yn = 'Y'
group by 
ka.vhost,
ka.SFDC_ACCOUNT_KEY, 
ka.count_units, 
s.RECORD_TYPE_NAME,
s.vplus_stage, 
s.screenings_enabled_date,
s.screenings_first_use_date,
sd.most_recent_screen_date
order by ka.vhost);