5 Commits

Author	SHA1	Message	Date
Samir Talwar	1e1a36a192	server/tests-py: Use environment variables for services in queries. ... I'm trying to shore up the Python integration tests to make them more reliable. In doing so, I noticed this. --- Rather than hard-coding hostnames and ports, we can (and already do) inject these into the HGE process using environment variables. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5255 GitOrigin-RevId: 6bb593999ece42cedef6619f31f9d9b2e39f30ef	2022-08-03 20:05:46 +00:00
Naveen Naidu	abb57e58c8	server/MSSQL: Event Delivery System (Incremental PR - 3) ... </details> PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3392 Co-authored-by: Divi <32202683+imperfect-fourth@users.noreply.github.com> GitOrigin-RevId: 9df6b0aa7d91f22571b72d3e467da23b916c9140	2022-04-21 07:20:34 +00:00
Karthikeyan Chinnakonda	44347d2d74	server: template the schema and table names in the event trigger PG functions ... Earlier, while creating the event trigger's internal postgres trigger, we used to get the name of the table from the `TG_TABLE_NAME` special trigger variable. Using this with normal tables works fine, but it breaks when the parent table is partitioned because we associate the ET configuration in the schema only with the original table (as it should be). In this PR, we supply the table name and schema name through template variables instead of using `TG_TABLE_NAME` and `TG_TABLE_SCHEMA`, so that event triggers work with a partitioned table as well. TODO: - [x] Changelog - [x] unit test (ET on partition table) GitOrigin-RevId: 556376881a85525300dcf64da0611ee9ad387eb0	2021-01-06 20:22:34 +00:00
Swann Moreau	5bc0355bdd	[server] coalesce multiple run_sql calls in tests (#270) ... GitOrigin-RevId: abd7303aaf8e7a8739fd10574249aec450082ef8	2021-01-06 16:07:22 +00:00
Tirumarai Selvan	c42af444f7	implement query to update an event trigger (#367)	2018-09-19 17:42:57 +05:30