Silvan

Good evening (at least in Switzerland 😄) @you1996 thanks for your suggestion. I'm currently focusing on my exams. I will have a closer look at it in the middle of...

hi @you1996 the problem I want to address with this issue is a bit bigger than just one form. At the moment the backend returns different error types. An error...

At the moment the priority of this enhancement is low for us.

Proposals for manipulating events: The only database-user which can manipulate (update) events is eventstore. The fields in `data`-column will be overwritten with the default values (`purge_data`). In all variants a...

> Why don't we store the default data on the IAM aggregate? > […](#) > On Tue, 13 Oct 2020 at 11:00, Silvan ***@***.***> wrote: Proposals for manipulating events: The...

### encryped fields The service which calls the eventstore encrypts the fields before they are sent to the eventstore. hard to implement because key rotation, events have to be changed...

@fgerschwiler, @livio-a and I discussed and decided for the following solution: We will implement "as event in IAM-aggregate" in a transaction save way. all updates of the existing events will...

hi @buehler Thanks for this enhancement. We will schedule it on Wednesday and update the issue.

hi @virth thanks you for your report. We will have a look at it. cheers

> Hopefully this also solves the problem where proto fields used in the query path are also listed in the body If not by default there might be an option...