Does it support nested data on the `fields` declaration?
See original GitHub issueAs a django-piston user, it is common to have nested data on the fields declaration:
fields = (
'id', 'username',
('group', ('id', 'name'))
)
On django-tastypie, this is similar to use full = True
on ForeignKey fields.
Is there a way to work with nested data?
Issue Analytics
- State:
- Created 10 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Use nested and repeated fields | BigQuery - Google Cloud
Best practice: Use nested and repeated fields to denormalize data storage and increase query performance. Denormalization is a common strategy for ...
Read more >BigQuery Explained: Working with Joins, Nested & Repeated ...
In this post, we will focus on joins and data denormalization with nested and repeated fields. Let's dive right into it!
Read more >Tutorial: Querying nested data with Amazon Redshift Spectrum
Amazon Redshift Spectrum supports querying nested data in Parquet, ORC, JSON, ... nested loop, which is followed by SELECT choosing the fields to...
Read more >How to declare nested data object in java? - Stack Overflow
Yes, it uses more code, and it can be more complicated. You have to describe the types. That is the price you pay...
Read more >Nested data support · Issue #3975 · great-expectations ...
This concept could be applied to nested fields that have multiplicity, notice residences is now an array. If we wanted to check every...
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
It would be great if you would support this natively since i think that feature will be used very frequently!
This should be easier to implement as of Restless 2.0.0, at least in terms of abstraction & less pain. A custom
FieldsPreparer
subclass could override theprepare
method (https://github.com/toastdriven/restless/blob/master/restless/preparers.py#L42-L60) & change behavior based on if thelookup
is adict
or a string.I’m still thinking about if I want to support this natively (maybe a
NestedFieldsPreparer
). Possibly in Restless 2.1.0.