Skip to content

Conversation

@vmikhailenko
Copy link
Contributor

@vmikhailenko vmikhailenko commented Feb 6, 2026

Opens a FAQ section with one nasty corner-case that we discovered internally. Just so we can later reference to it.


## Tips and Tricks

### Entities from imported services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this section rather focus on avoid expensive joins by providing the foreign key to associated entities instead of associated entity values (example with user name)? The name can be resolved when reading the logs on basis of the id.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We never documented the runtime manipulation of changelog.

I could add a little explainer. Something like: if you need custom identifier, write an handler...

Copy link
Contributor

@BraunMatthias BraunMatthias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the remote scenario is not valid - it's rather about how to deal with associated entities with best possible performance. User (as Remote) would be a nice example: the user.id FK can be resolved at READ time of the ChangeLog, but creation of logs would be much cheaper if no join is required to Users.

@@ -440,9 +440,8 @@ You can query the change log entries via CQN statements, as usual.

### Entities from Remote Services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optimize Changelogs for Associated Entities

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants