DBI schema management does not support multiple columns on constraints. #17

New issue

Closed

opened 2017-07-24 05:58:41 +00:00 by jamie · 4 comments

jamie commented

2017-07-24 05:58:41 +00:00

(Migrated from git.hazaar.io)

I have a project that uses a UNIQUE constraint with multiple columns. Whenever the table is created from scratch the constraint is created with only the first column.

This appears to be a snapshot issue at a minimum. The definition created by the snapshot is:

"request_data_request_id_name_key": {
  "table": "request_data",
  "column": "request_id",
  "type": "UNIQUE"
}

This definition should have multiple columns. In this case, request_id and name.

There may also be an issue with the replay not supporting multiple columns.

I have a project that uses a UNIQUE constraint with multiple columns. Whenever the table is created from scratch the constraint is created with only the first column. This appears to be a snapshot issue at a minimum. The definition created by the snapshot is: ```json "request_data_request_id_name_key": { "table": "request_data", "column": "request_id", "type": "UNIQUE" } ``` This definition should have multiple columns. In this case, *request_id* and *name*. There may also be an issue with the replay not supporting multiple columns.

jamie commented

2017-07-24 06:01:16 +00:00

(Migrated from git.hazaar.io)

changed the description

jamie commented

2017-07-24 06:01:58 +00:00

(Migrated from git.hazaar.io)

changed the description

jamie commented

2017-07-25 02:35:15 +00:00

(Migrated from git.hazaar.io)

added ~161 label