-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vector not deriving serde::Serialize & serde::Deserialize #6
Comments
Hi @turulix, thanks for the suggestion. I'd like to keep |
Yes, but this requires a lot of work as a user since you have to manually convert between the Vector type and the Vec. This is a problem when using serde since there is no really clean way of doing this as far as im aware of. And deriving the two traits, this would be done automatically by serde. If you want to keep this simplistic, maybe put this feature behind a feature flag that isn't enabled by default but available as a quality or life feature |
As mentioned above, since I mean, this is a datatype fgs. It is not weird to expect that people will want to serialize it. |
Made a fork which implements the Serialize & Deserialize in case you need it https://github.com/turulix/pgvector-rust |
Damn! Saw this a little late. I just did the same. Published as pgvec. |
Oh sweet, i'm just gonna use yours then, since I didn't publish mine :) |
Added a |
As the title says, would it be possible to derive Serialize & Deserialize for the Vector, so you can simply Serialize it into a json string using serde?
The text was updated successfully, but these errors were encountered: