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.

Sign up for GitHub

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

Jump to bottom

Restrict foreign key choices to prevent foreign keys across blocks #4

Open
neuromusic opened this issue Jul 1, 2013 · 1 comment
Open

Restrict foreign key choices to prevent foreign keys across blocks #4

neuromusic opened this issue Jul 1, 2013 · 1 comment

Comments

@neuromusic
Copy link
Member

Even though segments & recording channel groups do not have to point to a block, if they are defined, there are some Foreign Keys that should be restricted.

  • If a RecordingChannel is already pointing to a RecordingChannelGroup that is part of a Block, then it should not be able to link to RecordingChannelGroups from other blocks
  • If a SpikeTrain is associate with a Block through its segment, it should not be able to comprise a Unit that is not part of the same Block (through the RecordingChannelGroup)
@neuromusic
Copy link
Member Author

I don't think this can be done in the model definition... I think it can only be done on form validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@neuromusic