Extending a driver?

[salacr]

I wonder is there a way how to extend a driver?
The new version of PostgreSQL is strict about the output of pg_stat_activity. And only admin can view running queries..
I created a function for developers (they aren't working as admins for good reasons). So they can use
SELECT * FROM pg_stat_activity_for_all(); (that uses security definer feature so they see all running queries)

Now it will be really great to enable that functionality in adminer. I understand that it never will be in core so I would like to override a function:

	function process_list() {
		return get_rows("SELECT * FROM pg_stat_activity ORDER BY " . (min_version(9.2) ? "pid" : "procpid"));
	}

without need of copy whole class. Is't possible?

Thanks!

[vrana]

Extending a driver is not supported and I don't want to support it.

There's a list of routines in the schema overview and they can call the function from there. But I assume you want them to see this result from &processlist=, right? Are they also allowed to kill the queries? It's the main added value of this page.

I guess it would be possible to call adminer()->processList() in processlist.inc.php with the default implementation od returning process_list().

[salacr]

Yes, for convenience it would be great to have old behaviour back, so I would like to override the &processlist= page (well not whole page just the query, I believe you understand).

It would be nice to have the possibility to override kill query as well, but that's not so common, so I believe that DEVs can live with that.

The last paragraph is something I don't understand TBH. Is there actually a way how to rewrite whole page? (processlist) or?

[vrana]

By the last paragraph, I meant: You can prepare a pull request that will call adminer()->processList() in processlist.inc.php instead of process_list(). Then you can override this method in a plugin.

[salacr]

That would be nice!
#1079