12
rozważyć następujące zapytanie:kolumna "statement_date" jest nieaktualny typu ale wyrażenie jest typu INTEGER
INSERT INTO statement_line_items
SELECT count(*)::integer as clicks, sum(amount_cents)::integer as amount_cents, imps.user_id, imps.created_at::date as statement_date
FROM impression_events imps
INNER JOIN transactions t ON t.event_id = imps.id
AND t.event_type = 'ImpressionEvent'
AND amount_cents >= 0
WHERE imps.created_at >= (now() - interval '8 days')::date
AND imps.created_at < (now() - interval '7 day')::date
AND imps.clicked = true
GROUP BY imps.user_id, imps.created_at::date;
To jest powrót:
ERROR: column "statement_date" is of type date but expression is of type integer
LINE 2: ...icks, sum(amount_cents)::integer as amount_cents, imps.user_...
^
HINT: You will need to rewrite or cast the expression.
********** Error **********
ERROR: column "statement_date" is of type date but expression is of type integer
SQL state: 42804
Hint: You will need to rewrite or cast the expression.
Character: 117
Moja struktura tabeli za statement_line_items jest:
"id"; "integer"
"user_id"; "integer"
"statement_date"; "date"
"description"; "character varying(255)"
"clicks"; "integer"
"amount_cents"; "integer"
"created_at"; "timestamp without time zone"
"updated_at"; "timestamp without time zone"
Ach, byłem pod wrażeniem, że wprowadzony do tej samej nazwie kolumny. To wyjaśnia to. –
Dla mnie instrukcja insert, która działała, to: 'INSERT INTO statement_line_items (col1, col2, ...) wybierz data_for_col1, data_for_col2, ... od xyz'. Korzystam z usługi Amazon Redshift. –