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
Implement support for hidden attributes. These attributes will be prefixed with an underscore and not displayed. DataJoint may store metadata like creation timestamps, usernames, etc in the hidden attributes. U
Requirements
DataJoint will support hidden attributes in tables. Any attribute whose name begins with a _ will not be displayed and will not appear as part of the reverse-engineered table definition.
DataJoint declaration will allow declaring such attributes for internal purposes but the user API will be prohibited (by default) from using them.
Hidden attributes will not participate in joins.
Hidden attributes will not be included in results of user queries
Hi @dimitri-yatsenko - What protections did you have in mind when you envisioned that the user API would prohibit using hidden attributes? How would a super user circumvent this protection?
@A-Baji - Do you have a sense of your timeline for #1091? I think it could be really useful for something I'm working on
Hey Chris! I think that PR has just been waiting for a review from @dimitri-yatsenko. If any changes are requested feel free to PR to me with the fixes as I'm not currently working on any of the open source projects.
Feature Request
Problem
Implement support for hidden attributes. These attributes will be prefixed with an underscore and not displayed. DataJoint may store metadata like creation timestamps, usernames, etc in the hidden attributes. U
Requirements
_
will not be displayed and will not appear as part of the reverse-engineered table definition.Justification
The text was updated successfully, but these errors were encountered: