Composite PK from SQL loses order when translated to dbml about dbml HOT 2 CLOSED

Hi state303,

Due to an oversight, the fields order of composite primary keys is currently also the order in which the fields are defined in the table.

For your case, as a workaround, you can try changing the column order so that artist_id is defined before url_hash. Like this:

CREATE TABLE IF NOT EXISTS artist_url (
  artist_id INTEGER NOT NULL CONSTRAINT fk_artist_url_artist_id_artist REFERENCES artist,
  url_hash INTEGER NOT NULL,
  url VARCHAR(2048) NOT NULL,
  PRIMARY KEY (artist_id, url_hash)
);

from dbml.

Fixed in #416

from dbml.