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
The @ sign was used for referencing records because of similarities to social media or slack handles when using unqualified names, eg. @kevin. But when qualifying with a table (and schema) and column it looks like an email addresses, eg. [email protected].
Questions:
Is this bikeshedding? Yes.
Is this a thing to change?
What should it be instead, a # sign? #kevin or schema.person#kevin.name might be better and # as indicating an 'id' has precedence in html/css
Should it just be @schema.table.record.column? Might be more consistent across its various forms, ie. @record.column, @table.record.column, and @schema.table.record.column
The text was updated successfully, but these errors were encountered:
The
@
sign was used for referencing records because of similarities to social media or slack handles when using unqualified names, eg.@kevin
. But when qualifying with a table (and schema) and column it looks like an email addresses, eg.[email protected]
.Questions:
#
sign?#kevin
orschema.person#kevin.name
might be better and#
as indicating an 'id' has precedence in html/css@schema.table.record.column
? Might be more consistent across its various forms, ie.@record.column
,@table.record.column
, and@schema.table.record.column
The text was updated successfully, but these errors were encountered: