If a table (e.g. a staging/interface table) has a auto incrementing id set as the primary key (PK), Sesam cannot be used.
It cannot supply the value, since it is generated, and if the PK-column is not specified in the config, it is auto discovered via the table metadata (and fails because of a missing PK).
The main goal of Sesam is to keep the data in equal state, but as an integration engine, it would be nice to support this pattern.
Please sign in to leave a comment.