pg_dump --schema-only --create <database-name> -f <output-file>
(doc of pg_dump: https://www.postgresql.org/docs/12/app-pgdump.html). Not completely sure if --create
helps during the restoring process, but it sounds like it doeslet 🤔 = func();
🤔?
pg_dump --schema-only --create <database-name> -f <output-file>
(doc of pg_dump: https://www.postgresql.org/docs/12/app-pgdump.html). Not completely sure if --create
helps during the restoring process, but it sounds like it does pg_dump --schema-only --create <database-name> -f <output-file>
(doc of pg_dump: https://www.postgresql.org/docs/12/app-pgdump.html). Not completely sure if --create
helps during the restoring process, but it sounds like it does impl Trait
in both argument and return position with different meaningimpl Trait
in both argument and return position with different meaning impl Trait
in argument position means "any object that implements Trait can be passed here" and impl Trait
in return position means "only one concrete struct implementing Trait can be returned here"RwLock<()>
had a chat about it for a while on the rust discordBEGIN EXCLUSIVE
tokio::sync::mpsc
thread_init
is any harder to read there is nothing to discuss, but given they are equally readable we already use one in the codebase, no need to introduce another one