query_unchecked! still makes some checks

[7596ff]

I am in the early stages of creating my database schema. I am using barrel, refinery, postgres for migrations, and sqlx for my actual queries. When I need to make a change to my database, as I am in testing, I drop the database and run migrations again. Migrations are part of my startup process: my program connects to my database with a single postgres crate connection, runs migrations, then opens a sqlx PgPool. The migrations are barrel sql definitions, stored in refinery migration files according to their spec. Never mind for now that sqlx and refinery do not mix, I am not worried about it.

I can not start my program without selectively commenting out every sqlx::query_unchecked!() instance because compile-time checking will complain that the relation does not exist, even though I will be running migrations that creates the relation/table/etc.

My question: Why is it that a macro named query_unchecked still performs checks? Is there any way to convince sqlx that my database will have such fields once the migrations are ran?

[abonander]

I agree that the naming choice is slightly misleading, however, generating the anonymous record type still requires the query to be prepared (which requires a valid schema) so we can pull information about its output columns. The "unchecked" part is that we don't assert that the types of bind parameters are correct.

In #249 I have an implementation that allows you to save query preparation data so that you don't need a live migrated database to compile, which should hopefully be released in 0.4 soon.

In the meantime, keep in mind you're not obligated to use the macros. We have some examples of how to do dynamic queries in the README: https://github.com/launchbadge/sqlx#querying

A 100% "unchecked" query macro would be little more than a trivial wrapper around these, which seems kinda pointless to me. The _unchecked suffixed macros only really exist as a temporary workaround for some limitations on type checking in the current implementation. I hope to remove them in the not too far flung future.

[7596ff]

Thanks kindly. I understand the query and query_as functions more now that I have seen them from a different angle.

[abonander]

If you'd like to try the offline mode, I've got instructions here: #249 (comment)