Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support of composite PKs #18

Open
mfranck opened this issue Dec 7, 2012 · 0 comments
Open

Support of composite PKs #18

mfranck opened this issue Dec 7, 2012 · 0 comments
Milestone

Comments

@mfranck
Copy link

mfranck commented Dec 7, 2012

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" queries
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant