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

Interleaved table relationships are not included in a generated snapshot #85

Open
olavloite opened this issue Apr 7, 2021 · 0 comments
Labels
known limitation Known limitation or unsupported feature that cannot easily be supported

Comments

@olavloite
Copy link
Collaborator

Descripton:

Interleaved table relations are not included in generated change logs when taking a snapshot of an existing database.

Steps to reproduce:

Use for example DDL as below to create new table on Spanner:

CREATE TABLE TEST (
  TEST_LOC STRING(8) NOT NULL,
) PRIMARY KEY(TEST_LOC);

CREATE TABLE TEST_CONTNT (
  TEST_LOC STRING(8) NOT NULL,
) PRIMARY KEY(TEST_LOC),
  INTERLEAVE IN PARENT TEST ON DELETE CASCADE;

Then run:
liquibase --url="jdbc:cloudspanner:/projects/<project>/instances/<instance>/databases/<database>" --changeLogFile=changeLog.yml generateChangeLog

The generated change log will contain both tables, but the INTERLEAVE IN PARENT clause of the child table will not be generated.

Originally reported in #78. The problem that these relations were generated as a nameless foreign key has been fixed.

@olavloite olavloite added the known limitation Known limitation or unsupported feature that cannot easily be supported label Apr 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
known limitation Known limitation or unsupported feature that cannot easily be supported
Projects
None yet
Development

No branches or pull requests

1 participant