-
Notifications
You must be signed in to change notification settings - Fork 31
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
updating doc record with object name as email address doesnt work #55
Comments
Hi @si458 , I'm sorry I don't understand exactly your issue, are you saying that when you update a document's field with an email address, it fails silently? |
yes sorry for explaining it badly i tried my best, edit: |
right i forgot to add a func to out call and turns out nedb doesnt like full stops! fuck...
|
I think it is because of the dot |
@tex0l yeh refer to #55 (comment) |
The obvious workaround is to encode the email address in base64 |
thats a HUGE database change tho, oh poo, as we use the format of |
I'm sorry about that, this is a breaking change we've introduced due to #27 |
Actually no, it is not a breaking change! The initial nedb implementation already has this limitation What #27 introduced is the impossibility to use commas |
the issue existed in the original nedb project, and also a forked version, |
thanks for your help tho @tex0l ! |
@tex0l if i remove the line below, my app works, no issues so far! Line 31 in 68279cc
any chance you could add an option to IGNORE full stops, when i initialise a database? this would allow us to move to your repo/version and also upgrade to async properly! |
Unfortunately no as nedb uses the dot notation for referencing deep keys in objects, please read this section of the documentation: https://github.com/seald/nedb?tab=readme-ov-file#basic-querying |
thanks @tex0l i just discovered this before, we do use deepkeys for stuff, |
Describe the bug
when we try to update a doc record when an email address as the object name, its not updating
To Reproduce
will provide example when i create one, im using an existing project of ours so very complex
DOC RECORD FOUND BEFORE UPDATE:
DOC RECORD WHAT I WANT TO BE UPDATED
Expected behavior
for the record to be updated
Actual behavior
record isnt updated
Logs
Any log you can provide that showcases the problem.
Environment info
Additional context
we use to use https://github.com/louischatriot/nedb
then moved to https://github.com/yetzt/forked-nedb
now moving again to https://github.com/seald/nedb
The text was updated successfully, but these errors were encountered: