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
Queries can be written much more compactly if strings don't require quotation marks. I like this in that it's consistent with URL-style query notation. However, this increases ambiguity.
For example, should we allow albums?artist=Moby or require albums?artist="Moby"?
If we do not require quotation strings, anything number-like would be cast to a number, and anything boolean-like would be cast to a boolean. The ability to override via quotes would still be accessible.
The text was updated successfully, but these errors were encountered:
Queries can be written much more compactly if strings don't require quotation marks. I like this in that it's consistent with URL-style query notation. However, this increases ambiguity.
For example, should we allow
albums?artist=Moby
or requirealbums?artist="Moby"
?If we do not require quotation strings, anything number-like would be cast to a number, and anything boolean-like would be cast to a boolean. The ability to override via quotes would still be accessible.
The text was updated successfully, but these errors were encountered: