Assuming you want both headers and items to have notes, I'd do something like this and let aspects handle things (unmanaged associations).namespace someNamespace;
entity Documents {
key ID : String @Core.Computed;
status : String(100) not nu...
You want notes to depend on items, and items to depend on headers? I'm confused because there's an association in headers to notes, but notes includes a key association to items.
I tested it on a project and it does behave like that. I think the handler in the generic provider may be just checking if the property has any value at all, since these types are stored as NCLOB in SQL (see preview), if you use an empty array the db...
