Re:Show HN: Natural-SQL-7B, a strong text-to-SQL model
by gavinray on Monday February 05, 2024 @12:07PM
(#39263559)
Lets get even more cursed then:
CREATE TEMP TABLE temp_results(value int, value_squared int);
DO $$
DECLARE
r int;
BEGIN
FOR r IN SELECT generate_series FROM generate_series(1,5)
LOOP
INSERT INTO temp_results VALUES (r, r * r);
END LOOP;
END$$;
SELECT * FROM temp_results;
Re:Show HN: Natural-SQL-7B, a strong text-to-SQL model
by fifilura on Monday February 05, 2024 @12:27PM
(#39263805)
Uw you win, I guess. Already started to think what I would write in that code review comment ;)
Re:Show HN: Natural-SQL-7B, a strong text-to-SQL model
by koolba on Monday February 05, 2024 @03:12PM
(#39266452)
At the very least mention that re-running the SELECT in the same connection would include the prior results as well because they are preserved across commands within the same connection.
Re:Show HN: Natural-SQL-7B, a strong text-to-SQL model
by ttfkam on Monday February 05, 2024 @03:05PM
(#39266361)
Ha! plpgsql's seemingly sole purpose is to inject imperative code into a set-based environment. Probably does it more smoothly than most pl languages, but that's at the cost of imperative clarity.
But you're right. Postgres does allow for-loops like this. (They're also slower than the equivalent set-oriented approach.)
It's sets all the way down. A set of f(x) is still a set.