You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Make "id" more abstract than column < int >
- Support of composite PKs is mandatory to map data values inside association-classes
- Support of composite FKs may be optional, as composite PKs are mostly used in tables that represent relationships (possibly holding data values too). Those kind of tables rarely need to be referred as "to-one" roles.
- Support of composite PK may require that access to ids as integer would then be forbidden, even in private code...
Possible interface & implementation:
- Composite PK's components are stored as column< int >
- PK's components are registered using several calls to identity(string field_id,T::member *f)
- => several column_t may have is_id == true
- "is_id" is checked to produce "where" clauses in "search by ids" queries
The text was updated successfully, but these errors were encountered:
Requirements
- Make "id" more abstract than column < int > - Support of composite PKs is mandatory to map data values inside association-classes - Support of composite FKs may be optional, as composite PKs are mostly used in tables that represent relationships (possibly holding data values too). Those kind of tables rarely need to be referred as "to-one" roles. - Support of composite PK may require that access to ids as integer would then be forbidden, even in private code...Possible interface & implementation:
- Composite PK's components are stored as column< int > - PK's components are registered using several calls to identity(string field_id,T::member *f) - => several column_t may have is_id == true - "is_id" is checked to produce "where" clauses in "search by ids" queriesThe text was updated successfully, but these errors were encountered: