Re: Bug #661: Update to previous bug report
От | Joel Burton |
---|---|
Тема | Re: Bug #661: Update to previous bug report |
Дата | |
Msg-id | JGEPJNMCKODMDHGOBKDNGECPCNAA.joel@joelburton.com обсуждение исходный текст |
Ответ на | Bug #661: Update to previous bug report (pgsql-bugs@postgresql.org) |
Список | pgsql-bugs |
You can use case-sensitive identifiers (like your "AlbumList" by putting double quotes around them. CREATE VIEW "Foo" ... will create a view called Foo, whereas CREATE VIEW Foo or CREATE VIEW foo both create a view called foo So, to access your AlbumList, just do SELECT FROM "AlbumList" ... To delete it, DROP VIEW "AlbumList". Doesn't seem to be a bug at all, just a misudnerstanding of the role of quoted system identifiers in SQL. HTH. Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton Knowledge Management & Technology Consultant > -----Original Message----- > From: pgsql-bugs-owner@postgresql.org > [mailto:pgsql-bugs-owner@postgresql.org]On Behalf Of > pgsql-bugs@postgresql.org > Sent: Tuesday, May 07, 2002 11:52 PM > To: pgsql-bugs@postgresql.org > Subject: [BUGS] Bug #661: Update to previous bug report > > > Jacob (jacobpage@hotmail.com) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > Update to previous bug report > > Long Description > I discovered that PGAccess created the view by directly > manipulating the pg_class system table. I was able to remove the > view with "DELETE FROM pg_class WHERE relname = 'AlbumList';." > Perhaps constraints should be placed on the system tables to > disallow invalid data. (Or perhaps I can stop using beta tools :) > > Sample Code > > > No file was uploaded with this report > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org >
В списке pgsql-bugs по дате отправления: