Skip to content
Snippets Groups Projects
  1. May 19, 2001
  2. Apr 28, 2001
    • Bruce Momjian's avatar
      In create_function there is a remark concerning SQL/PSM not · 82511e33
      Bruce Momjian authored
      being ratified as yet. This is certainly no longer true, it wasn't
      even true in Q2/1998 when I did a little research for Date's book.
      SQL/PSM had been published on 1996-12-15 as ISO/IEC 9075:4. So you
      might want to update that section.
      
      
      Frank Wegmann
      82511e33
  3. Dec 26, 2000
  4. Nov 20, 2000
    • Tom Lane's avatar
      Revise handling of oldstyle/newstyle functions per recent discussions · 5bb2300b
      Tom Lane authored
      in pghackers list.  Support for oldstyle internal functions is gone
      (no longer needed, since conversion is complete) and pg_language entry
      'internal' now implies newstyle call convention.  pg_language entry
      'newC' is gone; both old and newstyle dynamically loaded C functions
      are now called language 'C'.  A newstyle function must be identified
      by an associated info routine.  See src/backend/utils/fmgr/README.
      5bb2300b
  5. Nov 02, 2000
  6. Oct 05, 2000
  7. Aug 25, 2000
  8. Jul 22, 2000
  9. Mar 27, 2000
  10. Mar 26, 2000
  11. Oct 02, 1999
  12. Sep 28, 1999
    • Bruce Momjian's avatar
      I have been working with user defined types and user defined c · 9394d62c
      Bruce Momjian authored
      functions.  One problem that I have encountered with the function
      manager is that it does not allow the user to define type conversion
      functions that convert between user types. For instance if mytype1,
      mytype2, and mytype3 are three Postgresql user types, and if I wish to
      define Postgresql conversion functions like
      
      I run into problems, because the Postgresql dynamic loader would look
      for a single link symbol, mytype3, for both pieces of object code.  If
      I just change the name of one of the Postgresql functions (to make the
      symbols distinct), the automatic type conversion that Postgresql uses,
      for example, when matching operators to arguments no longer finds the
      type conversion function.
      
      The solution that I propose, and have implemented in the attatched
      patch extends the CREATE FUNCTION syntax as follows. In the first case
      above I use the link symbol mytype2_to_mytype3 for the link object
      that implements the first conversion function, and define the
      Postgresql operator with the following syntax
      
      The patch includes changes to the parser to include the altered
      syntax, changes to the ProcedureStmt node in nodes/parsenodes.h,
      changes to commands/define.c to handle the extra information in the AS
      clause, and changes to utils/fmgr/dfmgr.c that alter the way that the
      dynamic loader figures out what link symbol to use.  I store the
      string for the link symbol in the prosrc text attribute of the pg_proc
      table which is currently unused in rows that reference dynamically
      loaded
      functions.
      
      
      Bernie Frankpitt
      9394d62c
  13. Jul 22, 1999
  14. Jul 06, 1999
  15. Jun 14, 1999
  16. May 20, 1999
  17. Dec 29, 1998
  18. Oct 30, 1998
  19. Sep 16, 1998
  20. Sep 07, 1998
  21. May 13, 1998
Loading