Support for EXCLUDE USING

[deem0n]

Hi, I just tried your code on the production database with 10,000 objects. Seems exclude constraints were not yet implemented, so here is my attempt to fix it. I am not as efficient with Smalltalk as with PL/pgSQL ;-)

With this fix I have loaded all objects from the DB fine!

[deem0n]

Also, pg_constraint.conkey may have colIndex = 0. That means that a function was used.
like in this snippet:

ALTER TABLE vcp.attachments
ADD CONSTRAINT unique_vcp_attachment_task_constr
EXCLUDE USING gist (dataset_id WITH =, metric_id WITH =, location_id WITH =,
   period_type WITH =, user_id WITH =, assignee_id WITH =,
  tstzrange(start_time, expiration_time, '()') WITH &&)
WHERE (attachment_type = 'vcp-task');

tstzrange(start_time, expiration_time, '()') WITH && will be referenced as column with index 0

[juliendelplanque]

Hello,

First of all, thank you very much for your contribution!

I'm happy to read that you were able to import your schema.

Your change seems to be ok but there are several details to fix:

• FmxSQLExclusionConstraint should not be hand-written. In fact the classes forming the meta-model are generated from a script (this is the way the meta-modelling framework works). I can help you to write the part of the script generating this constraint.
• The objects with Sql as prefix are part of another project on which depends FamixNGSQL, PgMetadata (https://github.com/olivierauverlot/PgMetadata). So SqlExclusionConstraint should be committed there.

[deem0n]

Julien, I definitely need help with FmxSQLExclusionConstraint magic and will rework SqlExclusionConstraint moving it into correct repo.

[deem0n]

Hi, added SqlExtrusionConstraint into PgMetadata: olivierauverlot/PgMetadata#9

[deem0n]

Hi, it was merged into PgMetadata: olivierauverlot/PgMetadata#9

Any advise on next steps?