tag:blogger.com,1999:blog-8839574367290288724.post8951963009931195267..comments2023-12-11T13:13:11.330-08:00Comments on Pavel Stehule's blog: Why you need plpgsql_check (if you write procedures in PLpgSQL)Pavel Stěhulehttp://www.blogger.com/profile/01996484227228696817noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8839574367290288724.post-20179951010256315472020-08-14T01:00:30.356-07:002020-08-14T01:00:30.356-07:00@vikram- edbspl has closed sources, so I cannot to...@vikram- edbspl has closed sources, so I cannot to support this language. Plase, try to contact your EDB supportPavel Stěhulehttps://www.blogger.com/profile/01996484227228696817noreply@blogger.comtag:blogger.com,1999:blog-8839574367290288724.post-2821514670295024112020-06-24T03:35:41.846-07:002020-06-24T03:35:41.846-07:00Hi greetings from India,
Can we use plpgsql_check...Hi greetings from India,<br /><br />Can we use plpgsql_check for testing procedures in edb (language edbspl) or user defined packages in edb postgres.<br /><br />Thanks in advance. vikramhttps://www.blogger.com/profile/04957406213668085201noreply@blogger.comtag:blogger.com,1999:blog-8839574367290288724.post-3939470144949194722019-09-02T00:28:40.244-07:002019-09-02T00:28:40.244-07:00Cool! I like injections test! So we need now dedic...Cool! I like injections test! So we need now dedicated out of the box “code coverage” case I think. Just run test and get report. There would be tricky stuff about SQL plans (how to cover different tree path throw all possible plans) but we have to start from something.Mishahttps://www.blogger.com/profile/01258035879534788204noreply@blogger.com