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
Over my patch #15 concerning "bind variable" (or sql parameters), I have several ideas of follow-up patches :
"sql normalization" (in advance)
optional sql parameter notation (":" prefix, ":a_dataframe") for tables to upload to sql,
"we can query native sql tables"
sql tables can have been created by previous sql requests,
so keep "table not found" message only if a table name has the ":" prefix notation,
"accept several sql orders"
result is feeded with the last sql instruction that gave a query result,
"uploaded tables don't overtstep sql native tables"
tables uploaded from python space tables are created with a dedicated prefix, like "tmp",
tables uploaded from python space are removed at the end of the sql orders.
Are you favorable for any of those 4 (+ #15) ideas ?
The text was updated successfully, but these errors were encountered:
Hi Greg,
Over my patch #15 concerning "bind variable" (or sql parameters), I have several ideas of follow-up patches :
optional sql parameter notation (":" prefix, ":a_dataframe") for tables to upload to sql,
sql tables can have been created by previous sql requests,
so keep "table not found" message only if a table name has the ":" prefix notation,
result is feeded with the last sql instruction that gave a query result,
tables uploaded from python space tables are created with a dedicated prefix, like "tmp",
tables uploaded from python space are removed at the end of the sql orders.
Are you favorable for any of those 4 (+ #15) ideas ?
The text was updated successfully, but these errors were encountered: