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
val player =DBPlayer(owner, team.teamId)
database.playerCollection.insertOne(player)
Furthermore, I'm having to call UUID#toString because it would otherwise try to use the internal Serializer again and not be able to find the right document
val player =DBPlayer(owner, team.teamId)
plugin.database.playerCollection.updateOneById(owner.toString(), player)
Is this intentional behavior, or is this a bug? Because it seems rather inconsistent.
The text was updated successfully, but these errors were encountered:
The typealias trick will not work. The way to go is to use registerSerializer, but I think it will not work for built-in type below. I will provide a fix in next kmongo release.
I have this
data class
in my Project:SerializableUUID is a typealias for UUID with my own Serializer:
When I now try to save an instance of
DBPlayer
like this,playerCollection
being a CoroutineCollectionIt will use the internal UUIDSerializer of KMongo and not the one that I specified.
But when I use insertOne this is not the case:
Furthermore, I'm having to call UUID#toString because it would otherwise try to use the internal Serializer again and not be able to find the right document
Is this intentional behavior, or is this a bug? Because it seems rather inconsistent.
The text was updated successfully, but these errors were encountered: