Databases
StackOverflow2013
Postsdbo
POUser-friendly error messages when removing row with Foreign Key REFERENCE constraint
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUser-friendly error messages when removing row with Foreign Key REFERENCE constraint
    primarykey
    data
    text
    <p>What would be best practice to handle removal of db row that has FK REFERENCE constraint? My goal was to present more user-friendly error messages to the end-user. Note that I don<code>t want to delete department with employees and that I don</code>t want to have cascade delete on tables.</p> <p>For example if we have two tables:</p> <pre><code>-- Department table CREATE TABLE [dbo].[Department]( [Id] [int] IDENTITY(1,1) NOT NULL, [Name] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, CONSTRAINT [PK_Department] PRIMARY KEY CLUSTERED ( [Id] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] -- Employee table CREATE TABLE [dbo].[Employee]( [Id] [int] IDENTITY(1,1) NOT NULL, [Name] [nchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [DepartmentId] [int] NULL, CONSTRAINT [PK_Employee] PRIMARY KEY CLUSTERED ( [Id] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] GO ALTER TABLE [dbo].[Employee] WITH CHECK ADD CONSTRAINT [FK_Employee_Department] FOREIGN KEY([DepartmentId]) REFERENCES [dbo].[Department] ([Id]) GO ALTER TABLE [dbo].[Employee] CHECK CONSTRAINT [FK_Employee_Department] </code></pre> <p>And if one wants to delete row from department table, where this row is referenced in employee table. What should one do?</p> <ol> <li><p>Before executing DELETE statement, check if row is referenced in employee table and gracefully return error to GUI (with eployee list if necessary)</p></li> <li><p>Execute DELETE statement and do catch exception like: </p> <pre><code>catch (SqlException ex) { switch (ex.Number) case 547: HandleErrorGracefully() } </code></pre></li> <li><p>Some other way?</p></li> </ol> <p>Would be nice if someone have code/link to application sample ...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USIvan Milosavljevic
    1. USIvan Milosavljevic
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUser-friendly error messages when removing row with Foreign Key REFERENCE constraint
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPossible duplicate http://stackoverflow.com/questions/7944559/how-to-manipulate-sqlexception-message-into-user-friendly-message
      singulars
      1. POUser-friendly error messages when removing row with Foreign Key REFERENCE constraint
      1. USShantanu Gupta
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload