GoogleCloudPlatform/spring-cloud-gcp

Support @CreatedDate for Datastore auditing

Open

#534 opened on Jul 15, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (347 forks)auto 404
datastoregood first issuepriority: p3type: enhancement

Repository metrics

Stars
 (547 stars)
PR merge metrics
 (PR metrics pending)

Description

Migrated from: https://github.com/spring-cloud/spring-cloud-gcp/issues/1809

Currently we only support @LastModifiedDate, and do not support @CreatedDate because it's difficult to know if the entity is being created when saving unless we do a second request to check if that ID already exists. We also cannot rely on the entity ID being NULL, because the users can set the ID for new entities as well.

The proposal is to support @CreatedDate based on the NULL ID, and clearly document that it will not work if you set the ID manually.

@Alos

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.