We do support Macro-style functions, see #1129. Does this address your use case?

I wonder whether @alitrack meant support for the syntax CREATE OR REPLACE MACRO macro_name ..., which would match what's avaliable for VIEW. I think it'd be nicer than DROP followed by CREATE.

@jdf-id-au - What timing! I was just looking for exactly what you described.

Since it appears that it doesn't exist, I'll go ahead and use the DROP ... CREATE syntax, but I wouldn't want to use that on a database with multiple apps talking to it for fear of hitting a race condition.

CREATE OR REPLACE is just syntactic sugar for DROP and CREATE happening in the same transaction. Transaction isolation (as part of ACID) should prevent any race conditions as long as it is happening in the same transaction.

That makes sense. Thanks!