delta/postgresql.git/src/test/regress/sql/view_perms.sql, branch master git.postgresql.org: git/postgresql.git Remove bitrotten view_perms test. Add some similar test cases to 2002-05-19T15:13:20+00:00 Peter Eisentraut peter_e@gmx.net 2002-05-19T15:13:20+00:00 13cd9eb9b85f871d3ae88c92765001fbb2080fe6 privileges test. 
privileges test.
rename pgsql to postgres in regression. 1999-02-22T02:08:32+00:00 Bruce Momjian bruce@momjian.us 1999-02-22T02:08:32+00:00 47dd11bdd034a8afeab5e9a3ed12ddbebb475d25 






From: Jan Wieck <jwieck@debis.com>
1998-02-27T02:38:15+00:00

Marc G. Fournier
scrappy@hub.org

1998-02-27T02:38:15+00:00

877224154d0acd2818e3b6e957128de43dab00e8

    I thought it would be a good idea to ensure that the new view
    permission  model  will  not   get   broken   by   subsequent
    fixes/changes. So I wrote a little regression test for it.

    There  is  an  ugly thing in this regression test. It creates
    temporary a test user that is required  for  the  tests.  The
    user  is removed at the end of the test, but if sometimes the
    regression suite is aborted or crashes exactly here, the test
    user will lay around in the pg_shadow.  Don't have a clue how
    to get around.





    I thought it would be a good idea to ensure that the new view
    permission  model  will  not   get   broken   by   subsequent
    fixes/changes. So I wrote a little regression test for it.

    There  is  an  ugly thing in this regression test. It creates
    temporary a test user that is required  for  the  tests.  The
    user  is removed at the end of the test, but if sometimes the
    regression suite is aborted or crashes exactly here, the test
    user will lay around in the pg_shadow.  Don't have a clue how
    to get around.