Hi Meet,
I was wondering
1. If you have any progress updates since your last message?
2. If you have any further details on the schedule for the time in Seattle
in a week and a half? (including video conference details for those unable
to attend in person)
3. If myself or the other attendee
Lets concentrate on making expressions in filter calls and lookups as
expressions reality. When we have done that we can try out different
syntax approaches in 3rd party apps. Finally, after we have field
tested the approaches, we can merge something in to Django.
- Anssi
On Thu, Oct 1, 2015 at
> I think the `F('name').decode('utf-8')` syntax is a good candidate for
core.
When Django supports expression lookups, it will be possible to build
syntax sugar third-party library on top of it.
For example, it will be possible to implement dotted syntax for F objects:
UserModel.objects.filter
> On Oct 1, 2015, at 13:38, Anssi Kääriäinen wrote:
>
> +1 to not requiring all transforms to handle __underscore__ syntax.
+1
> I think what we want to do is allow users choose which syntax they
> prefer. The idea is that Django will support both JSONExtract('data',
> path=['owner', 'other_pet
