Bug: Support Needed for Complex Multi-Column Constraints

[MZaFaRM]

Description:

• The tool currently does not support complex constraints involving multiple columns. Specifically, it fails to handle constraints like CONSTRAINT unique_integration_per_user_integration_id UNIQUE (integration_id, user_id, integration_value). Such constraints are essential for ensuring data integrity in scenarios where uniqueness is required across a combination of multiple fields.

Example of the Problem:

• Here's an example constraint that the tool struggles with:

  CONSTRAINT unique_integration_per_user_integration_id UNIQUE (integration_id, user_id, integration_value)
  

  This constraint is meant to ensure that each combination of integration_id, user_id, and integration_value is unique across the table.

Steps to Reproduce:

1. Define a table schema that includes a complex multi-column unique constraint like the one above.
2. Run the tool to apply this schema to a database.
3. Observe the failure or error message that occurs.

Expected Behavior:

• The tool should be able to interpret and apply complex constraints involving multiple columns without errors, allowing for sophisticated data integrity rules in the database schema.

Actual Behavior:

• Currently, the tool fails to process such constraints, potentially leading to an incomplete schema creation or an error message (specific error details would be beneficial here).

Impact:

• This limitation prevents users from defining and enforcing advanced data integrity rules in their database schemas, which is a critical feature for many complex applications.