-
Notifications
You must be signed in to change notification settings - Fork 137
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
Unable to filter, when encrypted data in data base #465
Comments
Filtering is done either client-side or server-side depending on whether you're using ReactiveTable.publish on the server. If you're only using reactive-table to display data that's already published to the client, I would expect filtering to work, but I can't tell what the problem might be without a lot more information. If you're trying to filter on the server, I don't think it's possible - I don't know how ReactiveTable.publish would be able to do the decryption. |
Thank you for your reply |
Are you sure the problem is related to the encryption? There could be something else wrong with your field or filter configuration. |
ya i am sure because if i removed encrypted data from db then filtration work properly, that whole issue coming only due to encrypted data in db. then what's the solution please help. |
I think it may be solve with client side filtration but i am not getting any documentation regarding that so please share me link of documentation of client side filtration. |
If you aren't using ReactiveTable.publish on the server, it will use client-side filtering. Write your own Meteor.publish and Meteor.subscribe to get your collection onto the client, and use the Collection object as the |
In my data base having encrypted data but before publish i decrypt that data and it displays in reactive-table with decrypted data but if i want to filter that data then filtration is not working on that data.
please help and explain me how the filtration is work in reactive-table and what is the solution to overcome this problem.
thank you
The text was updated successfully, but these errors were encountered: