GaryAustin1
GaryAustin1
You need to do the cache busting string added at end with time. ?bust=95857573738 for now.
That should work, pretty sure based on my submit that is what I did. The browser and CDN will think it is a new file. I would only use it...
I could swear I tested the code below before, and it did not pass down to postgrest-js after the initial setup, but seems to work (at least for javascript, not...
I had a running project I just updated all the dependencies and now I get the above error on `` in dev. If I build it works fine. "@sveltejs/adapter-static": "^1.0.0-next.29"...
I was able to get moving at the moment doing this: https://github.com/floating-ui/floating-ui/issues/1588 modifying jspopper as described. Not a real fix,though.
Not sure sveltestrap can't solve it. See here: https://github.com/bestguy/sveltestrap/issues/463
You at a minimum need to upgrade supabase-js, 1.24 is from almost a year ago and there were alot of changes especially at the end of last year that changed...
Insert causes select policy violation due to select occuring before all insert triggers are finished
Just a quick glance, but is this right? select 1 from page_user where user_id = auth.uid() and page_id = **page.page_id** Page table does not have page_id column in your table...
Insert causes select policy violation due to select occuring before all insert triggers are finished
@steve-chavez will be the expert on this. But all you did by setting select policy to true is prove either SB has an issue with the select running too soon...
Insert causes select policy violation due to select occuring before all insert triggers are finished
@steve-chavez So just to clarify for my understanding. There is no actual select statement. The returning is part of the insert, which has to meet select policy during the insert...