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
..
Permission	allow session variables in operators which expect array input (#2475)	2019-07-10 15:49:58 +05:30
Relationship	recover from inconsistent database state (closes #231) (#1863)	2019-04-17 21:59:39 +05:30
Schema	fail on tracking table/function with name conflict (close #2020) (#2383)	2019-07-11 07:41:20 +00:00
Deps.hs	allow exposing postgres functions through GraphQL interface (close #333) (#1073)	2019-01-25 09:01:54 +05:30
EventTrigger.hs	manual event triggers (close #1687) (#2077)	2019-05-13 15:11:07 +05:30
Headers.hs	refactor to remove warnings especially with orphan instances (#1163)	2018-12-13 12:56:15 +05:30
Metadata.hs	cache remote schema's introspection query response (fix #1679) (#2089)	2019-07-08 11:21:41 +05:30
Permission.hs	allow session variables in operators which expect array input (#2475)	2019-07-10 15:49:58 +05:30
QueryCollection.hs	keep allowed queries in sync when collections are changed, fix #2221 (#2230)	2019-05-20 15:59:32 +05:30
QueryTemplate.hs	multiplexed subscriptions (#1934)	2019-04-17 15:18:41 +05:30
Relationship.hs	better change detection when altering foreign key constraints (fix #2060) (#2252)	2019-06-03 15:51:55 +05:30
RemoteSchema.hs	cache remote schema's introspection query response (fix #1679) (#2089)	2019-07-08 11:21:41 +05:30
Utils.hs	schema cache sync improvements (#2098)	2019-05-03 16:12:26 +05:30