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
I queried ?limit=10 by accident (it should be ?$limit=10 and noticed it threw a lambda/api gateway error. In theory, it should generate WHERE limit = 10, which should just throw a sql error. Indicates something failed and the error's being lost.
The text was updated successfully, but these errors were encountered:
The problem can't be as simple as, there's a query string variable defined for $limit but not limit? Is it deeper than that?
Also, limit doesn't seem like valid SODA, so I agree with your assessment of 'wontfix' if needed... this would be like a "typo convenience feature", no?
The reverse proxy puts anything that doesn't have a leading dollar sign as part of the where clause. It's probably because the where clause fields aren't wrapped in quotes or something, so the parser assumes it's thelimit.
I queried
?limit=10
by accident (it should be?$limit=10
and noticed it threw a lambda/api gateway error. In theory, it should generateWHERE limit = 10
, which should just throw a sql error. Indicates something failed and the error's being lost.The text was updated successfully, but these errors were encountered: