You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the great work on bonsaidb, it is a really nice project!
While working with it, I stumbled upon the following issue: Making a library for any database via the AsyncConnection trait is easy with generics. However, keeping those generics everywhere forces me to forward these to the library user as well in some types, making it unwieldy to use. I would like to have a dyn AsyncConnection object, but it forces me to specify the storage object as well, which I am unsure how to do and whether it is possible to be compatible with bonsaidb at the same time.
It would be great if there would be some enum that wraps all database types, which one can use internally without generics. Is there anything I missed, that I can use right now?
Thank you in advance!
The text was updated successfully, but these errors were encountered:
I started down an enum path already, but I don't think it's the right design decision. I think I need to come up with a way to Box dyn [Async]Connecitons instead -- but with all of the generic usage, that will be a little bit of a challenge.
I worked on this over yesterday and today, but it's a lot harder than it might seem at first glance. This is due to all the generic functions not being trait-object safe. That being said, it looks completely feasible to come up with a way to use methods like SerializedCollection::get and pass an &dyn Connection to it.
The amount of work required, though, is quite significant, and it introduces fun naming challenges. I'm going to move this from the next milestone, but I do want to add this someday.
Hi!
Thank you for the great work on bonsaidb, it is a really nice project!
While working with it, I stumbled upon the following issue: Making a library for any database via the AsyncConnection trait is easy with generics. However, keeping those generics everywhere forces me to forward these to the library user as well in some types, making it unwieldy to use. I would like to have a
dyn AsyncConnection
object, but it forces me to specify the storage object as well, which I am unsure how to do and whether it is possible to be compatible with bonsaidb at the same time.It would be great if there would be some enum that wraps all database types, which one can use internally without generics. Is there anything I missed, that I can use right now?
Thank you in advance!
The text was updated successfully, but these errors were encountered: