Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed scripts when using the container but were OK when run in AWS RS #4

Open
rdagumampan opened this issue Dec 30, 2021 · 0 comments

Comments

@rdagumampan
Copy link

CREATE TABLE public.__yuniql_schema_version(
    sequence_id  INT IDENTITY(1,1) PRIMARY KEY NOT NULL,
    version VARCHAR(512) NOT NULL,
    applied_on_utc TIMESTAMP NOT NULL DEFAULT(GETDATE()),
    applied_by_user VARCHAR(128) NOT NULL DEFAULT(CURRENT_USER),
    applied_by_tool VARCHAR(32) NOT NULL,
    applied_by_tool_version VARCHAR(16) NOT NULL,
    status VARCHAR(32) NOT NULL,
    duration_ms INTEGER NOT NULL,
    checksum VARCHAR(64) NOT NULL,
    failed_script_path VARCHAR(4000) NULL,
    failed_script_error VARCHAR(4000) NULL,
    additional_artifacts VARCHAR(4000) NULL,
    CONSTRAINT ix___yuniql_schema_version UNIQUE(version)
);
ERR   2021-12-30 21:32:40Z   Failed to execute run function. 42601: syntax error at or near "IDENTITY"
Diagnostics stack trace captured a Npgsql.PostgresException (0x80004005): 

It expects a 'dev' database in Redshift which is "postgres" in pgsql

SELECT 1 from pg_database WHERE datname = 'yuniqldb';

ERR   2021-12-30 21:35:45Z   Failed to execute run function. 3D000: database "dev" does not exist
Diagnostics stack trace captured a Npgsql.PostgresException (0x80004005): 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant