Jim_Knicely
Administrator
Jim_Knicely Administrator
Reactions
-
Re: renaming schema does not rename schema in tables default values function using sequence
This issue has been resolved in Vertica 10.0.0-3 released on 07/29/2020 (Issue: VER-73468) and will soon be fixed in Vertica 9.3.1-14 (not released yet). Release Notes: https://www.vertica.com/docs/R… (View Post)-1 -
Re: Loading in In active partition
Vertica will create a new partition key... Example: dbadmin=> CREATE TABLE t (c INT NOT NULL) PARTITION BY (c);CREATE TABLEdbadmin=> INSERT INTO t SELECT 201907; OUTPUT-------- 1(1 row)dbadmin=… (View Post)-1 -
Re: Am concatenating multiple rows using : col1||col2.... but I am getting null as one of the columns
@ahaldar1106: @Bryan_H's suggestion might be the better choice as COALESCE is an ANSI SQL-92 standard! dbadmin=> SELECT * FROM t; a | b | c---+---+--- A | | B(1 row)dbadmin=> SELECT coales… (View Post)0 -
Re: COPY data from a customer privided S3 bucket
You use IAM instead of setting the AWS id and secret key. But it looks like you are still setting those. So can you post the out put from he COPY command, including the error? (View Post)-1 -
Re: renaming schema does not rename schema in tables default values function using sequence
Okay, for now you will have to manually update the DEFAULT value to point to the sequence's new schema: Example: ALTER TABLE new_schema.test_table ALTER COLUMN id SET DEFAULT NEXTVAL('new_s… (View Post)4

















