Creating a composite primary key - possible?

ServiceStack.OrmLite SQL Server
1

Hello.

I’m trying to generate C# classes and ormlite migrations based on
a GraphQL schema, where a type might have multiple primary key fields.

For the cases where there is one primary key, it’s easy to just slap on the “[PrimaryKey]” attribute,
but for the cases with > 1 primary key, I’m not sure what to do.
My hope was of course that I could avoid having to write functions to identity
existing rows for inserts/updates/deletes, and being able to rely on ormlite to figure that out.

It seems there is some old documentation/old forum posts that indicate that
ormlite by design does not support composite primary keys.
If this is still the case, is there something I can still do to make ormlite understand
that for a certain class its primary key is a composite?

2

OrmLite’s Primary Limitation is that it only supports a Single Primary Key.

So you wouldn’t be able to create a table with Multiple Primary Keys or use Update or Delete APIs which rely on it, otherwise you can still query tables with multiple PKs.