Ticket #23 (closed task: fixed)

Opened 3 years ago

Last modified 17 months ago

Clarify behaviour of fields-to-delete

Reported by: bruno Owned by: evert
Priority: minor Milestone: 1.1
Component: Repository Version:
Keywords: Cc: lily-developers@…

Description

Some things that should be clarified on the Record javadoc (or the Repository.update javadoc):

  • What happens upon Repository.update() if a field is both present in the Record object and in the list of fields to the delete?
  • If the fields-to-delete takes precedence, will the repository then remove the field from the (returned) Record object?
  • Is the list of fields-to-delete cleared after Repository.update() ?

Change History

comment:1 Changed 3 years ago by bruno

  • Cc lily-developers@… added

comment:2 Changed 3 years ago by evert

  • Milestone set to ~1.0

comment:3 Changed 2 years ago by evert

  • Milestone changed from 1.0 to 0.3

comment:4 Changed 2 years ago by bruno

  • Milestone changed from 0.3 to 1.0

Let's first look into #93, and then expand the docs.

comment:5 Changed 2 years ago by evert

  • Milestone changed from 1.0 to 1.1

Added a clarification to the javadoc of Record#getFieldsToDelete that deleting a field will take precedence over updating a field. r4722

Moving this issue to 1.1 so it can be updated further wrt the fields that are put in the returned object once #93 has been resolved.

comment:6 Changed 17 months ago by bruno

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.