Skip to content
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.

Sever Side Paging in required areas #787

Closed
DritonGoxhufi opened this issue Jul 26, 2022 · 3 comments · Fixed by #792
Closed

Sever Side Paging in required areas #787

DritonGoxhufi opened this issue Jul 26, 2022 · 3 comments · Fixed by #792
Assignees

Comments

@DritonGoxhufi
Copy link
Contributor

DritonGoxhufi commented Jul 26, 2022

Server-side paging should be implemented in at least the following areas:

  • Notifications -> Event History
  • Secure Connections

example PR: #730

@etschelp
Copy link
Contributor

etschelp commented Jul 27, 2022

Order of importance:

  1. Event History
  2. Connections
  3. Proof Templates
  4. Schemas

For the proof templates keep the search on top of the table, and use:

Page<BPAProofTemplate> findByNameLike(String name, Pageable pageable);

such as the s param of the PaginationCommand class.

As a next step we probably need to add a search by name to all tables again mainly:

  • connections
  • wallet, credentials and documents
  • presentation and credential exchanges
  • schemas

@schlagtim
Copy link
Contributor

#788

@etschelp
Copy link
Contributor

etschelp commented Aug 3, 2022

If Page<BPAProofTemplate> findByNameLike(String name, Pageable pageable);does not work in case name is empty you can use the Query annotation: Query("select * from bpa_proof_template where name like '$1%'")

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants