Databases
StackOverflow2013
Postsdbo
POConflict at update/insert on table which has nvarchar indexed relationship
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConflict at update/insert on table which has nvarchar indexed relationship
    primarykey
    data
    text
    <p>I have tables on sql server like below:</p> <pre><code>:: LG_STATUSES - code / nvarchar(50) - name / nvarchar(100) - description / nvarchar(250) :: LG_PACKAGES - LOGICALREF / int - PersonnelRef / int - lgStatusCode / nvarchar(50) // and some other columns which are not related to current problem </code></pre> <p>Lines of Statuses table:</p> <pre><code>code name description ------------------------------------------------------------ approved onaylandı NULL draft taslak NULL inApproval onay sürecinde NULL </code></pre> <p>When I create relationship between these two tables (Statuses.code &amp; Packages.lgStatusCode) by using Microsoft SQL Server Management Studio, there is no error. Relationship is created without problem. But when I try to insert new lines or update current line on Packages table by changing lgStatusCode</p> <pre><code>UPDATE [dbo].[LG_PACKAGES] SET [lgStatusCode] = 'draft' WHERE LOGICALREF = 101 </code></pre> <p>an error occured like below:</p> <pre><code>The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_LG_PACKAGES_LG_STATUSES". The conflict occurred in database "PackageManagement", table "dbo.LG_STATUSES", column 'code'. </code></pre> <p>I couldn't figure out the problem. 'draft' status is also exist in LG_STATUSES table. Does the error occurs because of using string (nvarchar) on relationship? Is this invalid usage?</p> <p>Thanks.</p> <p>Edit: SQL Contraint Definition</p> <pre><code>ALTER TABLE [dbo].[LG_PACKAGES] WITH CHECK ADD CONSTRAINT [FK_LG_PACKAGES_LG_STATUSES] FOREIGN KEY([lgStatusCode]) REFERENCES [dbo].[LG_STATUSES] ([code]) GO ALTER TABLE [dbo].[LG_PACKAGES] CHECK CONSTRAINT [FK_LG_PACKAGES_LG_STATUSES] GO </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBilal
    1. USBilal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CONo obvious reason I can see there can you select from lgstatuses where code = 'draft'? thinking may be 'draft ' or maybe different collations or some such
      singulars
      1. POConflict at update/insert on table which has nvarchar indexed relationship
      1. USTony Hopkinson
    2. COThat, and 50-character codes seem overly long. If it's not something like a short ISO code (say, the 3-letter country codes), I'd prefer a numeric code; anything above 10 characters (and anything with accents/non-ASCII-alphanumerics) is probably asking for trouble.
      singulars
      1. POConflict at update/insert on table which has nvarchar indexed relationship
      1. USClockwork-Muse
    3. COPerhaps your relationship is created in the wrong direction. Can you post the SQL constraint definition?
      singulars
      1. POConflict at update/insert on table which has nvarchar indexed relationship
      1. USGordon Linoff
 

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