Re: proposal: plpgsql pragma statement
От | Dmitry Igrishin |
---|---|
Тема | Re: proposal: plpgsql pragma statement |
Дата | |
Msg-id | CAAfz9KN_U22Uvv6M4ToGzt+O=T7jjyKA4-14io2At6AU4R+uqA@mail.gmail.com обсуждение исходный текст |
Ответ на | proposal: plpgsql pragma statement (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: proposal: plpgsql pragma statement
|
Список | pgsql-hackers |
вт, 4 дек. 2018 г. в 20:13, Pavel Stehule <pavel.stehule@gmail.com>: > > Hi > > I wrote plpgsql_check https://github.com/okbob/plpgsql_check. > > It is working well, but because it does static analyse only, sometimes it can produces false alarms or it should to stopa analyse, because there are not necessary data. > > https://github.com/okbob/plpgsql_check/issues/36 > > I see one possible solution in introduction of pragma statement with syntax: > > PRAGMA keyword [content to semicolon]; > > The pragma has a relation to following statement. So the issue 36 can be solved by pragma > > PRAGMA cmdtype CREATE; > EXECUTE format('CREATE TABLE xxx ... > > The PRAGMA statement does nothing in runtime. It works only in compile time, and add a pair of key, value to next non pragmastatement. This information can be used by some plpgsql extensions. > > What do you think about this proposal? I think it's a good idea in common. But how about multiple PRAGMAs? Consider PRAGMA cmdtype CREATE; PRAGMA objtype TABLE; EXECUTE format('CREATE TABLE');
В списке pgsql-hackers по дате отправления: