home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!uvaarpa!cv3.cv.nrao.edu!mail-to-news-gateway
- From: CS_PAUL@GSBVAX.uchicago.edu (Paul Ford 312/702-0335)
- Subject: re: Frequently Used Procedures
- Message-ID: <921117161141.23600e27@GSBVAX.uchicago.edu>
- Sender: daemon@nrao.edu
- Organization: National Radio Astronomy Observatory
- Date: Tue, 17 Nov 1992 22:11:41 GMT
- Lines: 34
-
- From: SMTP%"tjb@MATH.AMS.ORG" 17-NOV-1992 06:26:01.05
- To: info-ingres@MATH.AMS.ORG
- CC:
- Subj: Frequently Used Procedures
-
- Date: 17 Nov 1992 04:02:53 +0000 (GMT)
- From: mjm@gdwb.oz.au (Michael McGarrigle)
- Subject: Frequently Used Procedures
- To: info-ingres@MATH.AMS.ORG
- Errors-to: tjb@MATH.AMS.ORG
- Message-id: <3400@peking.gdwb.oz.au>
- Content-transfer-encoding: 7BIT
- Path:
- cv3.cv.nrao.edu!uvaarpa!darwin.sura.net!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!sol.deakin.OZ.AU!gdwb.oz.au!mjm
-
- Does anybody out there know of a way that commonly used
- routines can be stored in one place but accessed by
- several databases.
-
- i.e. We have an error handling routine that is called after
- every database access (To check for deadlock, etc) but it
- seems cumbersome to have to recreate this procedure for
- every database that we create.
-
- I am probably showing my ignorance but any ideas would be
- appreciated.
-
- Thanks in advance.
-
- --
- Michael McGarrigle Information Systems Division
- Email: mjm@gdwb.OZ.AU Geelong & District Water Board
- Phone: +61 52 262326 61-67 Ryrie St Geelong
- Fax: +61 52 218236 Victoria 3220 Australia
-