Ticket #2965 (closed defect: fixed)
Compound fields don't warn if sub_name isn't set and name is set
| Reported by: | tdb01r | Owned by: | |
|---|---|---|---|
| Priority: | unset | Milestone: | EPrints 3.2.3 |
| Component: | - | Version: | 3.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Sub-fields can defined with the same name if 'name' is used, which causes a database error.
Should Compound throw an error or warning if its subfields aren't sub-named?
Change History
Note: See
TracTickets for help on using
tickets.
