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
RBQL can now handle a.good_alphanumeric_column_name and a["arbitrary column name!"] notation (see #6 ).
But it would be great to go further and support direct column variables like name, surname, price etc without a and b prefixes.
It is not clear yet if it is possible at all to handle raw column names reliably and transparently. The most obvious problem is a potential conflict between column names and Python/JS identifiers, e.g. columns named class, if, sys, function, etc.
The text was updated successfully, but these errors were encountered:
RBQL can now handle
a.good_alphanumeric_column_name
anda["arbitrary column name!"]
notation (see #6 ).But it would be great to go further and support direct column variables like
name
,surname
,price
etc withouta
andb
prefixes.It is not clear yet if it is possible at all to handle raw column names reliably and transparently. The most obvious problem is a potential conflict between column names and Python/JS identifiers, e.g. columns named
class
,if
,sys
,function
, etc.The text was updated successfully, but these errors were encountered: