BUG: Updating a View Created Using Outer Join Causes GP Fault

Last reviewed: April 28, 1997
Article ID: Q104907

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
BUG# OS/2: 1773 (4.2)

SYMPTOMS

If a view is created by joining two or more tables using outer join, then issuing an UPDATE on the view may cause a general protection fault (GP fault).

For example, the following UPDATE command script will cause the problem:

   create table testM (m1 varchar(8) null, datam varchar(8) null)
   create table testC (datac varchar(8) null)
   go
   create view testview
   as
   select * from testM, testC where testM.datam =* testC.datac
   go
   insert testC values ("test")
   insert testM values ("hi","testo")
   go
   update testview set m1="help"
   go

WORKAROUND

You may update the base table directly instead of updating the view.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: trap nulls
Keywords : kbbug4.20 kbprg SSrvGPF SSrvServer
Version : 4.2
Platform : OS/2
Issue type : kberrmsg


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.