Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Activity for Andrewâ€
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Comment | Post #288339 |
The here string does work! (more) |
— | 11 months ago |
| Edit | Post #288779 |
Post edited: I meant "branches," not "copies" |
— | 11 months ago |
| Edit | Post #288779 | Initial revision | — | 11 months ago |
| Answer | — |
A: Possible drawbacks for having duplicate local sources of the project tracking the same Git remote You want `git worktree`: https://git-scm.com/docs/git-worktree. The idea is that you can have multiple branches of the same repository checked out to different directories, but they're still the "same" repository locally. I've used this technique precisely to avoid having to re-download `nodemodu... (more) |
— | 11 months ago |
| Edit | Post #288339 | Initial revision | — | 11 months ago |
| Answer | — |
A: Postgres command-line variable substitution error I don't know the "real" answer, but from `bash` on Linux at least, it's possible to work around the issue by using `-f` instead of `-c`, using process substitution to supply the SQL: ```bash $ psql -v foo=bar -f <(echo "SELECT :'foo' AS foo;") foo bar (1 row) ``` (more) |
— | 11 months ago |
| Edit | Post #288338 | Initial revision | — | 11 months ago |
| Question | — |
Postgres command-line variable substitution error According to the `psql` (version 14) man page, it's possible to set variables using the `-v` command-line parameter, then use the variable in a query, automatically quoted correctly, with `:'variablename'`. When issuing SQL commands with `-c`, this works: ```bash $ psql -v foo=bar -c "\echo :foo... (more) |
— | 11 months ago |