Some ideas about exposing functions

leto · May 4, 2010 · e6d4ab1 · e6d4ab1
1 parent ca5e9ac
commit e6d4ab1
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/IDEAS b/IDEAS
@@ -73,3 +73,9 @@ psql
  --pset tuples_only=true
  --set ON_ERROR_ROLLBACK=1
  --set ON_ERROR_STOP=1
+
+
+IDEAS FOR EXPOSING POSTGRES FUNCTIONS IN PL/PARROT
+* At minimum we need to expose a set of functions: elog(), and SPI stuff, and possibly even utility functions to get pieces of PostgreSQL data types that might not map cleanly to Parrot HLLs
+* One possibility is to create a PMC that people use to access PostgreSQL. This PMC would include methods corresponding to each of the functions we need to expose
+* Alternatively we can just make the functions available somehow. The primary advantage of PMC over this method as I (eggyknap) see it, is that it seems easier to figure out how to write a PMC than to figure out how to make functions magically available in PL/Parrot functions