Feature: Raise an error when query parameters are missing

[M1N0RM1N3R]

Is your feature request related to a problem?

To be frank, this one is related to my own ineptitude. 💀
I parameterize stuff like table names when working with my little Pydantic-based abstraction over surrealdb.py, for example:

SELECT * FROM type::table($tbl) WHERE user.id == $user_id AND timestamp > $timestamp

When I tried to use this query before, there was a parameter missing--the table name to search in ($tbl)--it defaulted to null and so it tried to search a non-existent table (NULL per my experimentation in Surrealist) so it returned nothing. It took me longer than I care to admit rummaging through log files to catch that bug.

Describe the solution

This one should be fairly simple: just make it so that an error is raised when there's a parameter declared in the query string, but no value--null or otherwise--is provided for it.

Alternative methods

You could implement this at the application layer by scanning the query string with a regex pattern like \$(\w*) and then checking if a value is provided for each param name found.

SurrealDB version

1.0.0+20230913.54aedcd for linux on x86_64

Contact Details

@m1n3r_spl on Discord

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[prabirshrestha]

+1. Hit the same issue and was scratching my head on why the query wasn't working as expected.

In my case I was refactoring the variable name. It was able to auto refactor all references for the rust code but not parameters.

[Reapimus]

Would be better if this were to be an opt-in/out per parameter or just a warning - I'm sure many people make use of the current behaviour for optional parameters in their queries.