Namespace awareness #33
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 milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
slendium/ocd#33
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 separate entities into namespaces. Frameworks could use such a feature to separate collections belonging to different modules using a different prefix.
An interface
Database\NamespaceAwareshould be added which allows specifying a mapping function fromEntityclass to full collection name. Without such a mapping,enforceSchema()cannot resolve foreign keys.The slendium/ocd-conformance-tests package should include tests to ensure namespace awareness is properly implemented.