3 ms·
> I didn't see anything to help me build back graphs Hmm you've certainly given me something to think about. Thanks. BTW joins are not challenging, but you ma
by bokwoon 4y ago
> I didn't see anything to help me build back graphs
Hmm you've certainly given me something to think about. Thanks.
BTW joins are not challenging, but you made me realize I didn't show any joins in my basic examples. Here is an UPDATE with JOIN in the meantime: https://bokwoon.neocities.org/sq.html#postgres-update-with-join https://bokwoon.neocities.org/sq.html#postgres-update-with-j....
- Fire-Dragon-DoL 4y agoThank you for the examples. I see the joins example, but they seem to be about creating queries, not mapping data. sql = "select blog.name, post.content, author.display_name from blog join post on blog.id = post.blog_id join author on post.author_id = author.id" Assuming the relationship: many blogs have many posts and posts have one author, I'd expect something along the lines of (sudo code): schemaOnTheFly = Blogs{}.HasMany(Posts{}.HasOne(Author{}) // Sorry the syntax for this doesn't really exist blogs := query.Exec(sql, params, schemaOnTheFly) fmt.Printf("%+v\n", blogs[0].Posts[0].Author) That's what I'd expect. Do notice that the schema is per-query, I'll let the developer handle the sharing portion of the schema (might be shared by a few queries)