how to set model if the table's primary key is multiple columns?

[italanchan]

check the demo source code, there is only one-column-based primary key, is the slayer support the multiple columns based primary key?

[ZmeiGorynych]

Not yet, we could add it if you have a usecase. Could you give an example of a schema and what kind of queries you'd want to make to SLayer on top of it where the composite primary key would matter?

[italanchan]

Invoice (PK: Office + Invoice No)
InvoiceItem (PK: Office + Invoice No + Item No)
InvoiceSubItem (PK: Office + Invoice No + Item No + Sub Item No)

from the global company view, it is require to analysis the product and sub product (which is the parts or additional parts for product).

[ZmeiGorynych]

I would say you could just model them as joins between the relevant individual columns; that would have to be defined manually (via some API, eg MCP), as auto-ingestion wouldn't pick them up. After all, SLayer doesn't enforce uniqueness or anything like that, it just generates the queries.

If you give the actual schema you need SLayer to work with, I'll see if there is a graceful way to support this in auto-ingestion as well.