-
Notifications
You must be signed in to change notification settings - Fork 72
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
It does not work at all. #152
Comments
Ah yes, I think you've found a bug that is triggered when input strings contain null bytes. Looks like it should be relatively straightforward to fix and improve performance as well.
Just running
One of the nice things about LocustDB is that you don't actually need to explicitly specify a schema, everything just happens automatically. There is some support for forcing columns to be interpreted as a certain type when loading data, see the |
Another thing I just noticed, some of the strange output is because |
Things seem to be working with the fix in #153:
|
I'm trying LocustDB on a clean Ubuntu 22.04 VM on AWS:
It's unclear how to preserve data upon restart.
It's unclear how to define table structure.
Nevertheless, a simple query after loading panics.
Also, it gives strange messages:
That makes me suspect it is not memory-safe.
The text was updated successfully, but these errors were encountered: