Wt

Hi Koen,

I am still facing a problem with a more "complex" database schema.

I have two tables "map" and "presentation" both have a composite primary key (columns "id" and "idMandator"). One "map" can have many "presentation"s and the foreign key in table "presentation" is a composite one consisting of a field "map_id" and again field "idMandator". Here is how it looks like:

create table map (

id integer not null,

"idMandator" smallint not null,

name text not null,

description text,

version int

);

alter table map add constraint pk_map primary key (id, "idMandator");

create table presentation (

id integer not null,

"idMandator" smallint not null,

aliasname text,

map_id integer,

version int

);

alter table presentation add constraint pk_presentation primary key (id, "idMandator");

alter table presentation add constraint fk_presentation_map foreign key (map_id, "idMandator") references map (id, "idMandator");

I added the "map" to a "presentation" like this:

Wt::Dbo::ptr mapPtr = session_.add(map);

Wt::Dbo::ptr presentationPtr = session_.add(presentation);

presentationPtr.modify()->setMap(mapPtr);

and wt creates an SQL statement as follows:

insert into "presentation" ("version", "idMandator", "id", "aliasname", "idMandator", "map_id") values ($1, $2, $3, $4, $5, $6)

This of course causes a Postgres error as: ...column "idMandator" specified more than once....

The issue is that the field "idMandator" in table "presentation" is part of the primary key as well as of the foreign key. Currently wt does not check for this case and simply adds and binds "idMandator" to the SQL statement again. So perhaps a fix could be just to check if a field with the same name is already bound to the SQL statement and in this case it won't be added again.

It would be great if you could fix this issue since it's the last obstacle left to use wt with composite primary / foreign keys.

Many thanks again,

Michael