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
I think such a constraint could be very useful to maintain not secret, but not-userfacing properties in a type. I propose to add hidden as boolean property constraint, in addition to mandatory, readonly, and notnull.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Dear All,
I recently found, as part of ZetaSQL, a constraint
hidden
, see https://github.com/google/zetasql/blob/master/docs/data-definition-language.md?plain=1#L204 , which would exclude the hidden properties from wildcard projections, ieSELECT * FROM mytype
orSELECT FROM mytype
in case of ArcadeDB.I think such a constraint could be very useful to maintain not secret, but not-userfacing properties in a type. I propose to add
hidden
as boolean property constraint, in addition tomandatory
,readonly
, andnotnull
.What do you think?
Beta Was this translation helpful? Give feedback.
All reactions