Embedding Some Relationships, but Not All
See original GitHub issueIs it possible to embed some of the relationships, but not all of them?
It seems like the embed
serializer is an all-or-nothing type of deal, without allowing for some relationships to be embedded and others to be “normal”. Weird as that requirement might be, it’s a situation we’re running into right now!
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Resource embedding on views doesn't work on N-to ... - GitHub
Work-around (not really usable in production environment):. in your PostgREST exposed schema, create tables (instead of views); start PostgREST, and check that ...
Read more >Embeddings in Machine Learning: Everything You Need to ...
The vector space quantifies the semantic similarity between categories. Embedding vectors that are close to each other are considered similar.
Read more >Embeddings: A Matrix of Meaning - Petuum, Inc. - Medium
An embedding matrix is a list of all words and their corresponding embeddings. A few things to keep in mind: Thinking in higher...
Read more >Word Embeddings - Language Jones
Even with messy data, there are some intriguing relationships: jawn is right between miss and sombody/sumn (and forms a triangle with somebody/ ...
Read more >Introduction to Knowledge Graph Embedding - dglke
TransE cannot cover a relationship that is not 1-to-1 as it learns only one aspect of similarity. TransR addresses this issue with separating...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yep I think function is best direction 👍 If I were starting over today that would probably be the “base” type since it’s the most flexible. Don’t think it’s a problem that it adds a new possible type for the value!
Absolutely! Making every configuration option able to be defined as a function – or even better, an async function – just adds so much flexibility. Definitely the way to go!