Implement num_entries, all_entries in DataStore

[mylibrar]

Is your feature request related to a problem? Please describe.
To integrate DataStore with DataPack, we want to add a few functions in DataStore to replace the previous implementation of all_annotations, num_annotations, etc.

Describe the solution you'd like
We want to add two functions

all_entries(entry_type_name)
num_entries(entry_type_name)

to DataStore. They should incorporate the functionalities of all the following DataPack methods:

• all_annotations
• num_annotations
• all_links
• num_links
• all_groups
• num_groups
• all_generic_entries
• num_generics_entries
• all_audio_annotations
• num_audio_annotations

Additional context

• num_entries should still return an integer. all_entries should now return an iterator of entry data in list format instead of class. To keep the old API signature, DataPack will need to convert the entry data into entry objects.
• This PR should be made to the master branch.

[hunterhector]

@wanglec will your "deletion" implementation affect this issue as well, what's your suggestion to proceed?

[wanglec]

It seems like we have to count None in non-annotation-like lists and use len(list) - count of None.

[hunterhector]

Let's create a number to hold the number of None, that would probably block this issue.

[hepengfe]

The current implementation is iterating all entries and count correctly. It seems like it's expected to record the count of all entry types and None type. In this sense, we need to have a dictionary {entry_type: count} and all entry add/remove methods will update the corresponding count?

[hunterhector]

Actually Lechuan’s suggestion sounds good that we record the num of none instead of recording the non-none, this way only delete function needs to update the number

On Sat, May 7, 2022 at 1:14 AM feipenghe ***@***.***> wrote: The current implementation is iterating all entries and count correctly. It seems like it's expected to record the count of all entry types and None type. In this sense, we need to have a dictionary {entry_type: count} and all entry add/remove methods will update the corresponding count? — Reply to this email directly, view it on GitHub <#767 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHYBNYNAU6Y7YH37ULAYEDVIX32HANCNFSM5US7ZYNA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Hector, Liu Zhengzhong Website: https://hunterhector.github.io/ LinkedIn: http://www.linkedin.com/pub/hector-zhengzhong-liu/23/115/406