How can I do a 'like' query or similarity search?
Is the structure from the auto-generated graph filters from some spec?
filter
and sort
a list inside a graph query.
I'm still kind of new to graph. Is this design/structure specific to any single frontend library like Rely or Apollo?...
Nested aggregates and calculations
use embedded fields inside expr
Ash JSON API is showing an error when following tutorial
ash_json_api
extension, I got the following error:
```
Compiling 18 files (.ex)
error: function plug/2 imported from both Phoenix.Router and Plug.Builder, call is ambiguous...Trying to better understand filter in the context of AshGraph
JSON-API And Calculations
Applying constraints to embedded union types
How to: Keyset pagination in AshJsonApi
** (KeyError) key :metadata not found in: #SomeAshResource..
** (KeyError) key :metadata not found in: #SomeAshResource..
DISTINCT ON LEAST() GREATEST()
Ash.Query.filter creates filter with OR condition instead of AND
Ash.Query.filter
function documentation explicitly says that a filter will be added with the AND
condition, but it seems that this is not the case when fragments
is used.
For example, if I do this:
```elixir...Generated filter expression is incorrect - BUG
Filter by struct keys in a read action
Transactions
Post.create_with_log(%{title: title})
Then in my Post resource file, I could possibly:
1) Create a code_interface
definition such as define(:create, args: [:title], action: :create_with_log)
...Keyset pagination doesn't seem to use default_limit value
Session params missing for oidc providers using response_mode: form_post (e.g. Azure AD)
response_mode: form_post
. This requires that the POST callback endpoint is not under CSRF protection (similar to how pow_assent
is doing it).
The issue is that the user/<strategy>
key is not in the session during the callback phase. Am I required to implement a server side session store as pow
does it?
See the setup below:
...Testing: How to approach testing
Why don't read actions filter by attributes?
warning: Changeset has already been validated for action :create.
Should I use old-fashioned DB lookup tables? What might be some alternatives?
relationships
. Would you recommend an alternative? I had considered for small sets to use a calculation, but I think that works with reads but not writes, right?...