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
{{ message }}
This repository was archived by the owner on Jan 8, 2026. It is now read-only.
The insert, update and delete functions in gramex.data often tend to fail silently when the args provided are incorrect or incompatible.
E.g.
Suppose x is an int, then doing
gramex.data.filter(**store, args={"col_1", [x]})
returns an empty dataframe if x is not a string, even if col_1 has been designated as an integer column. I guess this is because it's meant for FormHandler HTTP requests.
Here's another example:
gramex.data.delete(**store, args={'xyz': ["1"]})
If xyz is not a column of the table, this line deletes everything in the table.
We should ideally raise TypeErrors and KeyErrors respectively when the user provides wrong args. I'll settle for a warning too.
The
insert,updateanddeletefunctions ingramex.dataoften tend to fail silently when theargsprovided are incorrect or incompatible.E.g.
Suppose
xis an int, then doingreturns an empty dataframe if
xis not a string, even ifcol_1has been designated as an integer column. I guess this is because it's meant for FormHandler HTTP requests.Here's another example:
If
xyzis not a column of the table, this line deletes everything in the table.We should ideally raise TypeErrors and KeyErrors respectively when the user provides wrong
args. I'll settle for a warning too.