Data definition with entity relations #5
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Research
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No project
No assignees
1 participant
Notifications
Total time spent: 1 day 8 hours
Due date
c.fahner
1 day 8 hours
No due date set.
Depends on
#9 Size restrictions for text/binary/numeric types
slendium/ocd
#70 Make the entity ID a regular field
slendium/ocd
Reference
slendium/ocd#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently it is not possible to declare relationships between entities or indices on fields.
Schemaobjects should contain definitions of relationships to other entities.A field that is declared with an
Entitytype, should show up as a regular field in theSchemawith a type that can hold theidof the referenced entity. Requires #70 to be completed.Fields should also be declarable as unique or indexed. Non-entities should also be able to manually declare field(s) as its primary. Some of these indices can consist of multiple fields.
The issue of resolving the referenced
Entityobject by itsidhas moved to #66. Nesting objects inside a JSON field has moved to #67.I am removing the ability to set names for fields that don't match the parameter names. The gain is not worth the increased complexity (required checking for duplicates, inability to grab a small subset of fields since you have to check the entire list for duplicates). Making field names match parameter names also automatically prevents certain unsafe characters being used.
This makes #83 obsolete.