Support for dynamic auditor types [DATACMNS-1269]

[spring-projects-issues]

Lee Standen opened DATACMNS-1269 and commented

It would be useful if Spring Data JPA natively supported the ability for variant auditor types, based on the required data type for a field.

For example:

@Entity
public class Table1 {
  ...
  @CreatedBy
  Long createdBy; // stores a primary key identifier
  ...
}

And within the same project

@Entity
public class Table2 {
  ...
  @CreatedBy
  String createdBy; // stores the username

This would allow some legacy schemas (such as the one I'm dealing with) to be easily mapped

---

Referenced from: commits a778215, fc79c1c, 9a3b5b7, 47c8e5b, 819bce7

3 votes, 5 watchers

[spring-projects-issues]

Lee Standen commented

This is related to Stack Overflow post: http://stackoverflow.com/questions/23560015/any-way-to-have-spring-data-auditing-populate-long-or-string-depending-on-field

[spring-projects-issues]

Bradley Plies commented

Just a bump for this old ticket. I've encountered a situation while refactoring an app where this would have been great to have

[spring-projects-issues]

Oliver Drotbohm commented

That should work in Lovelace snapshots now. Just register multiple beans of type AuditorAware<…> an we will automatically select the right one based on the auditor type

[spring-projects-issues]

Oliver Drotbohm commented

I had to roll back the change as it was causing issues in downstream projects. We have RC2 coming in a day so that we have to postpone this a bit further

[AlexandreCassagne]

@oliviergierke Have you been able to re-introduce this change?

[odrotbohm]

Closing this in favor of #1352 because that had been created earlier. I'll leave a follow up comment on the other ticket.