Skip to content

Conversation

@nrdvana
Copy link
Contributor

@nrdvana nrdvana commented Nov 3, 2025

This adds support to the DBI parser for Postgres to read the user-defined stored procedures and triggers from the public namespace.

It has been tested on only two versions of postgres so far...
but I've been using it in production for quite a while.

This is independent of #182 which adds support to the SQL parser, but seems to omit the DBI parser.

@nrdvana nrdvana force-pushed the dbi_postgresql_procs_triggers branch from 857b2e9 to db1389a Compare November 3, 2025 18:01
This adds support to the DBI parser for Postgres to read the
user-defined stored procedures and triggers from the public
namespace.

It has been tested on only two versions of postgres so far...
@nrdvana nrdvana force-pushed the dbi_postgresql_procs_triggers branch from db1389a to 983be4a Compare November 3, 2025 18:07
/
) or die "Can't prepare: $@";

my $trigger_select = $dbh->prepare(<<SQL) or die "Can't prepare trigger query: $@";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to see the description what is the result of these two blocks of code: 'trigger_select' and 'procedure_select'. Eg. this block of code selects triggers and procedures from XXX which we can access later programmatically using YYY

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not entirely sure what I can say there... the code itself just prepares the query and follows the style of the code above it. I could comment more on what each field means, but the fields are generally matching the names used on the Trigger and Procedure objects.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just general comment what this block does and how we can use/access those results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants