CREATE OR UPDATE SHARE
complete
Ryan Boyd
If trying to script, you should do CREATE SHARE IF NOT EXISTS followed by UPDATE SHARE. you can then run the same script for the first execution as well as the nth execution.
T
Tino@MotherDuck
complete
CREATE OR UPDATE SHARE is now rolled out!
This post was marked as
in progress
Adrien Sales
Ryan Boyd
planned
As per Tino@MotherDuck, there is agreement this should happen.
Adrien Sales
Ryan Boyd: These are cool news, thanks a lot for kind feedbacks, keep going guys for good vibes and effortless datapipelines ;-p
T
Tino@MotherDuck
complete
Hi folks! We've updated this logic. Now you can update a share, and folks who are receiving the share automatically get the new data!
Adrien Sales
Tino@MotherDuck: WOW, thanks a lot, I'll give it a try very soon and probabl make a blog post about ti with a real life example 🚀
T
Tino@MotherDuck
Adrien Sales: we're working on making even this easier in coming weeks - producers of data will not need to run "update share" for receivers of data to get fresh data - it'll happen automatically!
Adrien Sales
Tino@MotherDuck: Btw, will also the documentation be updated ? https://motherduck.com/docs/motherduck-sql-reference/create-share
Adrien Sales
Tino@MotherDuck: For now, I cannot use "CREATE OR UPDATE SHARE "gardes_ncl_share";" : any tip to make it working ?
T
Tino@MotherDuck
Adrien Sales: Apologies - I misunderstood the request by not reading it carefully. The lead engineer on this and I agree that it makes sense to build out this logic here, we're in discussions on how to make it happen - stay tuned!
Adrien Sales
👍 for this one as it may make client code mush cleaner and light : we would not need to check anymore about checking if a share already exists, useful when having cron jobs that update data 🦥