graphql-engine/server/src-lib/Hasura/RQL/DDL/Utils.hs

module Hasura.RQL.DDL.Utils
  ( clearHdbViews
  ) where

import qualified Database.PG.Query as Q

import           Hasura.Prelude

clearHdbViews :: Q.Tx ()
clearHdbViews = Q.multiQ (Q.fromText clearHdbViewsFunc)

clearHdbViewsFunc :: Text
clearHdbViewsFunc =
  "DO $$ DECLARE \
   \ r RECORD; \
   \ BEGIN \
   \   FOR r IN (SELECT routine_name FROM information_schema.routines WHERE specific_schema = 'hdb_views' ORDER BY routine_name) LOOP \
   \     EXECUTE 'DROP FUNCTION hdb_views.' || quote_ident(r.routine_name) || '() CASCADE'; \
   \   END LOOP; \
   \ END $$; "
do not clean hdb_views by dropping and creating the schema (closes #567) (#568) Fix migration logic to accommodate for non superuser permissions. Closes #567 - [x] Server By clearing the `hdb_views` schema of existing views and functions instead of dropping and creating it again. - [x] Bug fix (non-breaking change which fixes an issue) 2018-09-28 13:52:54 +03:00			`module Hasura.RQL.DDL.Utils`
			`( clearHdbViews`
			`) where`
move raven into graphql-engine repo 2018-06-27 16:11:32 +03:00
explain a graphql query, similar to explain of an sql statement (close #562) (#805) 2018-10-19 05:15:28 +03:00			`import qualified Database.PG.Query as Q`
schema cache sync improvements (#2098) * build schema cache function without db setup The setup shouldn't happen for sync. The database is already setup by the instance which generated the event. This means that the sync is now faster. * use SQL loop to drop hdb_views schema views and routines with ordering This avoids deadlocks when schema is being changed concurrently * schema sync now only processes the latest event This becomes useful when a lot of schema change events happen while we are still processing an earlier event. 2019-05-03 13:42:26 +03:00
			`import Hasura.Prelude`
move raven into graphql-engine repo 2018-06-27 16:11:32 +03:00
add event triggers (#329) 2018-09-05 14:26:46 +03:00			`clearHdbViews :: Q.Tx ()`
Remove any outstanding hdb_views (fixes #3940) (#3965) 2020-03-26 23:42:33 +03:00			`clearHdbViews = Q.multiQ (Q.fromText clearHdbViewsFunc)`
add event triggers (#329) 2018-09-05 14:26:46 +03:00
schema cache sync improvements (#2098) * build schema cache function without db setup The setup shouldn't happen for sync. The database is already setup by the instance which generated the event. This means that the sync is now faster. * use SQL loop to drop hdb_views schema views and routines with ordering This avoids deadlocks when schema is being changed concurrently * schema sync now only processes the latest event This becomes useful when a lot of schema change events happen while we are still processing an earlier event. 2019-05-03 13:42:26 +03:00			`clearHdbViewsFunc :: Text`
add event triggers (#329) 2018-09-05 14:26:46 +03:00			`clearHdbViewsFunc =`
			`"DO $$ DECLARE \`
schema cache sync improvements (#2098) * build schema cache function without db setup The setup shouldn't happen for sync. The database is already setup by the instance which generated the event. This means that the sync is now faster. * use SQL loop to drop hdb_views schema views and routines with ordering This avoids deadlocks when schema is being changed concurrently * schema sync now only processes the latest event This becomes useful when a lot of schema change events happen while we are still processing an earlier event. 2019-05-03 13:42:26 +03:00			`\ r RECORD; \`
			`\ BEGIN \`
			`\ FOR r IN (SELECT routine_name FROM information_schema.routines WHERE specific_schema = 'hdb_views' ORDER BY routine_name) LOOP \`
			`\ EXECUTE 'DROP FUNCTION hdb_views.' \|\| quote_ident(r.routine_name) \|\| '() CASCADE'; \`
			`\ END LOOP; \`
			`\ END $$; "`