Michael J. Sullivan
Michael J. Sullivan
I've submitted https://github.com/pganalyze/libpg_query/pull/249
Before I dive in on this, does anybody have a more reduced query that triggers it?
Minimized: ``` module default { type Album { constraint std::exclusive on (.artist); link artist: default::Artist; }; type Artist; type Music { link album: default::Album; }; }; ``` and ``` with...
I am a "-0" on this; I don't like adding more complexity to our import system. But also I'd be happy to merge it. Let's make a decision on it...
The semantic question: Imagine a function like: ``` function make_user(name: str) -> User using (insert User { name := name }) ``` The behavior of `select make_user('Bob')` is clear, but...
Because the FOR makes it explicit. On Wed, Aug 28, 2024, 16:52 Elvis Pranskevichus ***@***.***> wrote: > I think we really do not want to have the number of inserts...
We should write some docs but this is done, right?
Huh, yeah. I think postgres does that so that there is a well defined order for its sorted indexes
How about binding `comp_date` with a `for`?
@themajashurka's second suggestion was what I was thinking of