Closed alexandru closed 5 years ago
Yes, this is the same as #766
@deusaquilus The PR that was meant to fix #766 has been merged however this issue is still cropping up with quill 3.4.3, is there something additional that needs to be done to fix the .onConflictUpdate
?
@alexandru Fix is now in quill latest snapshot, will also be available in next release.
Thanks a lot @mdedetrich, you've just made my day 🙂 since we had to change field names for working around this.
Cheers,
This is awesome! Thank you @mdedetrich!
-Alex
On Fri, Sep 6, 2019 at 4:51 AM Alexandru Nedelcu notifications@github.com wrote:
Thanks a lot @mdedetrich https://github.com/mdedetrich, you've just made my day 🙂 since we had to change field names for working around this.
Cheers,
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/getquill/quill/issues/1527?email_source=notifications&email_token=AAKOLCA3I2DJCTU3SEK56I3QIIK2BA5CNFSM4IE2Z7F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6CGR5I#issuecomment-528771317, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKOLCHVKKPRUYHMLXZMH2DQIIK2BANCNFSM4IE2Z7FQ .
So good to see this is fixed! Just hit that issue :D
I may have hit a variation on #766 but I'm not sure.
Consider this schema:
And the type is nothing out of the ordinary:
Things work (e.g.
filter
,insert
, etc), except foronConflictUpdate
:The error this fails with is:
What Quill does is to apply the NamingStrategy instead of my custom schema when updating that field.
The issue can be worked-around by renaming that field from
envISO639Language
toenvIso639Language
. But that's not possible in my case.Version:
3.3.0