-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
fix: Use correct notation for byte value in postgres #666
Conversation
@ikrivosheev @tyt2y3 @billy1624 - Just fyi I fixed the semantic issues clippy had with my PR. Please have a look when you get a chance! |
Please let me know if there is anything else needed from me. This fix is tied to a feature I've been trying to release, just wondering if I should start planning an alternative solution Thanks |
@ikrivosheev is there anything I can do to help push this one along? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you all |
@tyt2y3 @ikrivosheev I think I'll just reference this update by commit for now. How often are new releases published? |
It depends. Usually we'd batch together several PRs into a minor release every few weeks. |
🎉 Released In 0.30.1 🎉Thank you everyone for the contribution! |
PR Info
New Features
None
Bug Fixes
Value::Bytes
should write as byte string instead of bit string #459 (comment)Breaking Changes
None
Changes
None (aside from the bug fix described above)