bind params on queries

[ChuckHend]

• Using sqlx query! marcro, which uses bind parameters, and has compile time checks on the statements.
• use now() at time zone 'utc' from the database in the queries instead of computing time in the webserver
• dropped "IS TRUE" from the sql statements.

[ChuckHend]

I think this is going to change very soon right? This should probably return json formatted instead of just the name as a string.

[ianstanton]

Yes, in the cor-526 branch

[ianstanton]

Question about the timestamps. Everything else seems good. Thanks for the updates!

[ianstanton]

If we use (now() at time zone 'utc') here (updating version record) and below when we update the extension's updated_at timestamp, will we have slightly different values?

[ianstanton]

For example, if we assign time above we ensure the timestamps are the same when an extension version is updated. Similar for created_at timestamps:

[ChuckHend]

now() will stay the same within the transaction.

https://database.guide/how-now-works-in-postgresql/#:~:text=In%20PostgreSQL%2C%20the%20now(),when%20called%20without%20an%20argument).

[ChuckHend]

postgres=# begin;
BEGIN
postgres=*# select now();
              now              
-------------------------------
 2023-03-30 19:32:06.570287+00
(1 row)

postgres=*# select now();
              now              
-------------------------------
 2023-03-30 19:32:06.570287+00
(1 row)

postgres=*# commit;
COMMIT
postgres=# select now();
              now              
-------------------------------
 2023-03-30 19:32:23.667648+00

[ianstanton]

Makes sense! That's exactly what we want.