The idea is to improve the SQL language, specifically the join syntax, for the special but common case when joining on foreign key columns.
Example below taken from PostgreSQL documentation [1]
In SQL-89, we didn't have any JOIN syntax yet, so queries were written in this way:
Example notebook can be found here.
If you share this list, please use this link instead: https://lambdaurora.dev/optifine_alternatives
It may still be only a redirection link, but it will have a better web display of the list soon. And the list being on GitHub/GitHub pages improves load times.
The gist version of this list will stop being updated.
| \033[38;2;23;147;209m ▄ | |
| ▟█▙ | |
| ▟███▙ | |
| ▟█████▙ | |
| ▟███████▙ | |
| ▂▔▀▜██████▙ | |
| ▟██▅▂▝▜█████▙ | |
| ▟█████████████▙ | |
| ▟███████████████▙ | |
| ▟█████████████████▙ |
| use std::str; | |
| fn main() { | |
| // -- FROM: vec of chars -- | |
| let src1: Vec<char> = vec!['j','{','"','i','m','m','y','"','}']; | |
| // to String | |
| let string1: String = src1.iter().collect::<String>(); | |
| // to str | |
| let str1: &str = &src1.iter().collect::<String>(); | |
| // to vec of byte |
| export const POST = (auth) => ({ | |
| method: "POST", // *GET, POST, PUT, DELETE, etc. | |
| mode: "cors", // no-cors, cors, *same-origin | |
| headers: { | |
| "Content-Type": "application/json", | |
| ...(auth ? { "Authorization": auth } : {}) | |
| }, | |
| }) |
| /** | |
| * !!!! This code doesn't work anymore !!!! | |
| * | |
| * - You can check working code on comments. I won't update this code anymore. | |
| * | |
| * Also, I just decided to remove this code. You can check revisions for old code. | |
| * Since this code was made for discord client that almost 5 years ago, It seems like doesn't work anymore. | |
| * I don't want people keep arguing in the comments, i decided to remove this code. | |
| * | |
| * Note: This code is now fulfilled with Javascript comments. This code won't work even if you pasted to console. doesn't do anything. |
A modest proposal for a first-class destiny operator equivalent in Svelte components that's also valid JS.
Svelte 2 has a concept of computed properties, which are updated whenever their inputs change. They're powerful, if a little boilerplatey, but there's currently no place for them in Svelte 3.
This means that we have to use functions. Instead of this...
<!-- Svelte 2 -->
<h1>HELLO {NAME}!</h1>
