Marshmallow should support compound Primary Keys
Issue #101
on hold
Single primary key while optimal is not always the case especially with legacy data. It would be wonderful if Marshmallow had support for compound primary keys.
Is there a current workaround for this?
Comments (8)
-
-
reporter
Yes I get that. And we are totally on board with Single field Primary Keys for all our new development. We were just hoping that we could use Marshmallow for our legacy data also. It is OK though I would agree that on a project like this where none of you are getting paid, you have to pick your battles and supporting compound keys is a lost cause.
Thanks I had to ask :)
Todd
-
repo owner
- changed milestone to Future version
- changed version to 1.2 (develop)
-
assigned issue to
Linas Naginionis
-
repo owner
- removed responsible
- edited description
-
repo owner
- changed status to open
-
repo owner
- changed version to 1.2
-
repo owner
- removed milestone
Removing milestone: Future version (automated comment)
-
repo owner
- changed status to on hold
As already announced further development regarding new features and fixing non trivial bugs or design issues of the ORM will be put on hold.
- Log in to comment
- Assignee
- –
- Type
- Priority
- Status
- on hold
- Component
- Persistence
- Milestone
- –
- Version
- 1.2
- Votes
- 3
- Watchers
- 8
This could be quite a huge task because I intentionally designed MM to not support compound primary keys. Since currently I almost have no spare time (personal reasons) I can't predict when this feature could be implemented. It would be great if we could receive some thoughts or support from community on this issue...