Ajeet D'Souza 605f8633f3 fail on tracking table/function with name conflict (close #2020) (#2383) ... Currently, we allow tracking of a table with the same name as an already tracked function, and vice-versa. This causes an issue when querying from GraphQL since it will only query the table and not the function. I've made changes to disallow this by throwing an error.		2019-07-11 07:41:20 +00:00
..
event_triggers	manual event triggers (close #1687) (#2077)	2019-05-13 15:11:07 +05:30
graphql_introspection	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
graphql_mutation	allow session variables in operators which expect array input (#2475)	2019-07-10 15:49:58 +05:30
graphql_query	allow session variables in operators which expect array input (#2475)	2019-07-10 15:49:58 +05:30
graphql_validation	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
horizontal_scale/basic	sync metadata cache across multiple instances connected to same db (closes #1182) (#1574)	2019-03-12 11:16:27 +05:30
inconsistent_objects	recover from inconsistent database state (closes #231) (#1863)	2019-04-17 21:59:39 +05:30
logging	breaking: server logging changes (close #507, close #2171) (#1835)	2019-07-11 05:37:06 +00:00
remote_schemas	forward set-cookie headers from remote servers (fix #1654) (#2305)	2019-06-04 15:40:28 +05:30
subscriptions	live queries tests for subscription (#487)	2018-09-20 07:16:03 +05:30
v1	fail on tracking table/function with name conflict (close #2020) (#2383)	2019-07-11 07:41:20 +00:00
clear_db.yaml	python based tests (#387)	2018-09-18 11:51:57 +05:30