home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #18 / NN_1992_18.iso / spool / comp / database / ingres / 1193 < prev    next >
Encoding:
Text File  |  1992-08-20  |  4.4 KB  |  95 lines
  1. Newsgroups: comp.databases.ingres
  2. Path: sparky!uunet!paladin.american.edu!darwin.sura.net!convex!news.oc.com!spssig.spss.com!uchinews!gsbacd.uchicago.edu!cs_mj
  3. From: cs_mj@gsbacd.uchicago.edu (Mark Jaeger)
  4. Subject: Re:  Ownership problem. ABF application  
  5. Message-ID: <1992Aug20.160607.1@gsbacd.uchicago.edu>
  6. Lines: 83
  7. Sender: news@uchinews.uchicago.edu (News System)
  8. Organization:     
  9. References: <1992Aug12.002043.1970@candle.uucp> <1992Aug14.164610.1@gsbacd.uchicago.edu> <1992Aug20.161118.18014@emr1.emr.ca>
  10. Date: Thu, 20 Aug 1992 22:06:07 GMT
  11.  
  12. In article <1992Aug20.161118.18014@emr1.emr.ca>, kasvand@ccrs.emr.ca
  13. (Tony Kasvand) writes:
  14. >
  15. >   I have an image (and running executable) application which won't let other
  16. > users execute and use this program. They keep receiving this error at the
  17. > beginning:
  18. >
  19. > xlqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
  20. > xx SELECT on table special_users_table: no GRANT or GRANT compatible permit   x
  21. > xx exists. (E_US0DAE)                                                         x
  22. > xx (Tue Aug 18 09:02:21 1992)                                                 x
  23. > xx                                                        [PRESS RETURN]      x
  24. > xmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
  25.  
  26. Let's say your database is called "foodb".  You need to do this:
  27.  
  28.     $ sql foodb
  29.     grant all on special_users_table to public \g
  30.     \quit
  31.  
  32. This allows all users to do "select", "insert", "update", or "delete"
  33. on the table (as directed by the application).
  34.  
  35. >   OK, so I try to grant privileges to my database. I put this command into
  36. > the Default Frame ABF/4GL code (is it correct to do this? ...apparenty not)..
  37. >
  38. > grant db_admin on database tonis_ccrs_database to public;
  39. >
  40. >     The error I receive is:
  41. >
  42. > qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
  43. >  x You cannot GRANT or REVOKE database or installation privileges             x
  44. >  x  while in session with this database.                                      x
  45. >  x  Ensure your session is connected to the iidbdb database. (E_US188A)       x
  46. >  x (Tue Aug 18 08:59:52 1992)                                                 x
  47. >  x                                                        [PRESS RETURN]      x
  48. >  mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
  49. >
  50. >  I don't know where to find iidbdb .
  51.  
  52. The iidbdb is special database, but in many ways it's just like any
  53. other database.  If you really wanted to do what you state, then you
  54. should do this:
  55.  
  56.     <log into the INGRES account>
  57.     $ sql iidbdb
  58.     grant db_admin on database tonis_ccrs_database to public \g
  59.     \quit
  60.  
  61. However, this now gives the public the ability to do very destructive
  62. things to your database, such as "drop table special_users_table", which
  63. is probably not what you want.  You're better off using the
  64. table-specific grants.
  65.  
  66. >      While in ABF/4GL menus editing the application, i've tried to unlock
  67. > the database in menu options Utilities.LockStatus by using Delete which
  68. > should unlock the database (at least that what the Help says) but :
  69. >
  70. >
  71. > qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
  72. >  x You may not delete your own session.                                       x
  73. >  x  The row you are positioned on is the one corresponding to your own edit   x
  74. >  x session.  You may not delete locks corresponding to that session.          x
  75. >  x (E_AB00A6)                                                                 x
  76. >  x                                                        [PRESS RETURN]      x
  77. >  mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
  78.  
  79. The lock referred to in the message is a lock that helps prevent
  80. multiple ABF/4GL developers from colliding with each other while working
  81. on the same ABF application.  This does not apply to _users_ of the
  82. database who are using an application that you wrote.  
  83.  
  84. It's important to distinguish between access to the database, access to
  85. the tables, and access to an ABF application.  I'd like to suggest that
  86. you take one of the elementary INGRES developers classes.  There's also
  87. a lot of good information along these lines in the INGRES DBA Guide.
  88.  
  89. --Mark Jaeger                internet: cs_mj@gsbvax.uchicago.edu
  90. Graduate School of Business        yellnet:  (312) 702-0328
  91. University of Chicago            faxnet:   (312) 702-0233
  92. Disclaimer: My opinions are my own and not those of my employer.
  93. Ich bin ein Virus.  Mach' mit und kopiere mich in Deine .signature.
  94.  
  95.