In relation, project generate relation unique key instead primary.

[sheryarshirazi]

consider sql this SQL

CREATE TABLE cars (
    car_number int(11) NOT NULL,
    model varchar(255) NOT NULL,
        UNIQUE (model),
    PRIMARY KEY (car_number)
);

CREATE TABLE excise (
    chassis_number int(11) NOT NULL,
        vehicle int(11) NOT NULL,
    PRIMARY KEY (chassis_number),
        CONSTRAINT FK_of_excise_with_cars
        FOREIGN KEY (vehicle) REFERENCES cars (car_number)
);

excise table connect with cars table by vehicle and car_number respectively but generated JDL model has connect both entities with Excise.vehical to Cars.model. It should link with car_number instead model see JDL below

entity Cars(cars) {
    carNumber Integer required,
    model String required unique maxlength(255)
}
entity Excise(excise) {
    chassisNumber Integer required
}

relationship ManyToOne {
    Excise{vehicle(model) required} to Cars{excise}
}

why do it always prefer UNIQUE over primary key?

[Blackdread]

The logic seems correct and expected. I do not really understand the English you wrote, can you rephrase and fix typos?

JDL is using surrogate keys, I am not in favor of that but that's how the project works.

[sheryarshirazi]

@Blackdread corrected but I think you already explain the reason

[Blackdread]

I close this ticket, the logic is correct, and the (model) means that it use that data to be displayed in the dropdown in UI. Read JDL documentation for that