Skip to content

Conversation

@ChristophWurst
Copy link
Contributor

@ChristophWurst ChristophWurst commented Oct 10, 2025

A addressbook-query currently loads the full address book to filter in memory. Depending on the implementation it should be possible to push some of the filtering down to the implementation, e.g. to filter on a DB level first. This improves memory footprint and performance drastically.

I'm opening this as proof of concept and hope to get some input on the approach and whether this would be accepted.

The same mechanism exists for caldav, where I took inspiration from. For BC I chose to not add a new method to the carddav backend interface.

nextcloud/server#55669 shows what it will look like in an implementation.

@ChristophWurst
Copy link
Contributor Author

@phil-davis do you see any concerns with the approach?

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.

1 participant