Foreign key spec regressions
See original GitHub issueraised by @roll
- rc1 removed use of
"self"
for a self referencing foreign key, and instead used""
- rc1 removed references to data packages for foreign keys and it is now back
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
FactoryGirl blowing up spec due to foreign key in model
The models appear to have valid factories and pass all specs. But feature specs either blow up the foreign key relationship or don't...
Read more >Foreign Key Constraint | CockroachDB Docs
The `FOREIGN KEY` constraint specifies a column can contain only values exactly matching existing values from the column it references.
Read more >Testing foreign key contraints - Ruby on Rails - thoughtbot
When the database deals with cascading the foreign key deletion, there's no need for the dependent: :destroy option on the association and the ......
Read more >Basics Of MySQL FOREIGN KEY Constraint With Examples
This tutorial explains the basics of MySQL FOREIGN KEY Constraint such as its syntax, how to add, declare, drop, and change it with...
Read more >Foreign keys | YugabyteDB Docs
YSQL. A foreign key represents one or more columns in a table referencing the following: A primary key in another table.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rufuspollock it does make sense without data packages, now that we have a data resource specification. The FK just needs to be to any Data Resource, in a DP or not.
Ok. So the only change really was to update the schemas. done that in #473