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
Sometimes it would be nice to have a tool that stores binary data in the key data base. We could either integrate this functionality directly into kdb set or create a new tool with the name kdb setbinary, kdb setbin or a similar name. Since binary data can also contain NULL bytes I think we should probably support escape sequences to save arbitrary data. For example the command
kdb setbin user/test/binary/key '\x48\x69\x00'
or the equivalent command
kdb setbin user/test/binary/key 'Hi\x00'
could save the C ASCII string Hi(the numbers 72, 105, and 0) in the key user/test/binary/key.
The text was updated successfully, but these errors were encountered:
I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖
I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖
Proposal
Sometimes it would be nice to have a tool that stores binary data in the key data base. We could either integrate this functionality directly into
kdb set
or create a new tool with the namekdb setbinary
,kdb setbin
or a similar name. Since binary data can also contain NULL bytes I think we should probably support escape sequences to save arbitrary data. For example the commandkdb setbin user/test/binary/key '\x48\x69\x00'
or the equivalent command
kdb setbin user/test/binary/key 'Hi\x00'
could save the C ASCII string
Hi
(the numbers 72, 105, and 0) in the keyuser/test/binary/key
.The text was updated successfully, but these errors were encountered: