Project

General

Profile

bug #7022

TaxonName.protectedAuthorshipCache should initially be false

Added by Andreas Kohlbecker almost 2 years ago. Updated almost 2 years ago.

Status:
Rejected
Priority:
New
Category:
cdmlib
Target version:
-
Start date:
10/17/2017
Due date:
% Done:

0%

Severity:
normal
Found in Version:

Description

The default value of TaxonName.protectedAuthorshipCache is true. Since this cache is protected a user with the authority TAXONNAME.[CREATE] can not create and persist a new TaxonName without setting this field to false prior doing the flush (see #7021 for details). Therefore this field should be initially set to false. For many use cases it might be advisable to protect this field for usability reasons, but protecting it initially because of such considerations is too opinionated and breaks the principle of least surprise.


Related issues

Copied from Edit - bug #7021: CREATE permission not sufficient to save new TaxonName entity Resolved 10/17/2017

History

#1 Updated by Andreas Kohlbecker almost 2 years ago

  • Copied from bug #7021: CREATE permission not sufficient to save new TaxonName entity added

#2 Updated by Andreas Kohlbecker almost 2 years ago

  • Severity changed from critical to normal

#3 Updated by Andreas Kohlbecker almost 2 years ago

  • Description updated (diff)

#4 Updated by Andreas Kohlbecker almost 2 years ago

  • Description updated (diff)

#5 Updated by Andreas Müller almost 2 years ago

  • Assignee changed from Andreas Müller to Andreas Kohlbecker

Can you give more information why you think that
"The default value of TaxonName.protectedAuthorshipCache is true"?

In TaxonName it is

private String authorshipCache;

and therefore false in most implementations.

#6 Updated by Andreas Kohlbecker almost 2 years ago

  • Status changed from New to Rejected
  • Target version deleted (Unassigned CDM tickets)

You are absolutely right there is obviously no true set as default default for TaxonName.protectedAuthorshipCache. However, while working on #7021 the protectedAuthorshipCache was apparently always set to true, causing problems. I had to set it to false explicitly in my code make avoid problems, but not this has changed - very mysterious, but anyway we can close this ticket as invalid.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)