> I don't have a real problem with views/sprocs that provide
> SELECT * like some seem to have.
How about this sequence of lovely things:
-- DBA land
CREATE TABLE Candidate
(
Id INTEGER NOT NULL
, Name CHAR(40) NOT NULL
, DrivingPerk INTEGER
);
CREATE TABLE Perks
(
PerkId INTEGER NOT NULL
, Description CHAR(40) NOT NULL
);
CREATE VIEW PeoplesPerk
AS
SELECT
*
FROM Candidate
LEFT JOIN Perks
ON Candidate.DrivingPerk = Perks.PerkId;
-- this is client code... works now.
SELECT Name, Description FROM PeoplesPerk;
-- back to DBA land
ALTER TABLE Perks
ADD (Name CHAR(40) NULL);
UPDATE TABLE Perks
SET Name = Description;
-- and the same line from above now fails... simply because the view used a
SELECT *
SELECT Name, Description FROM PeoplesPerk;
Marc
===================================
This list is hosted by DevelopMentor� http://www.develop.com
Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles
http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at http://discuss.develop.com
