Hi Frans,

First of all congratulations on the new release!!

While upgrading one of my projects I encountered an issue during validation which was not a problem in V3.

For this (simplified) table:

CREATE TABLE [OrderItemsLink]
    (
      [OrderId] [int] NOT NULL ,
      [ItemId] [bigint] NOT NULL ,
      [ParentId] [bigint] NULL ,
      CONSTRAINT [PK_db33b5c4e9c844f3c0987f9e1df] PRIMARY KEY CLUSTERED
        ( [OrderId] ASC, [ItemId] ASC )
    )
GO

ALTER TABLE [OrderItemsLink]  WITH CHECK ADD  CONSTRAINT [FK_cc237dc4f1b8b98277dc5bb91f3] FOREIGN KEY([OrderId], [ParentId])
REFERENCES [OrderItemsLink] ([OrderId], [ItemId])
GO

the designer reports this error:

The relationship 'OrderItemsLink.ParentLink - OrderItemsLink.Contents (m:1)' has a foreign key field 'OrderItemsLink.OrderId (FK)' which points to itself, which isn't supported.

In V3 this was not reported, so perhaps the second part of the key is ignored in V4?

Regards, André

Hi André,

Yes, I reproduced the error message on v4. And yes, it worked before on v3.5. We will look into this (whether this is or not a new breaking change).

I do recall it was a restriction in earlier v3.5 but was lifted in later builds, but have to check. If that's the case we accidentally forgot to port it over to v4. In any case, we'll lift the restriction

Great!!

It was a restriction which was lifted on March 12th, 2012 in v3.1 and backported to v3.5, but apparently not to v4.0. We'll backport the changes to v4 as well.

Great!

I found no other issues so far, so when the fix is there I can start testing the performance gains.

Thanks!

The test in the was added in v4. The restriction I mentioned above was in the FK / relational model data which was lifted in v3.1, and that code is still present in v4.

The test added was added to find relationships which fully point to themselves, this was added during v4 beta. Your example shows the test is too strict, it should only raise an error if all fields point to themselves. We'll correct this mistake.

Thanks for the explanation!

Attached is a debug build of the applicationcore dll, which fixes the issue. please copy this into the installation folder as administrator and test whether this solves your problem. The final build will be out later today.

Thanks for the quick fix. I will test it this evening.

It is fixed.

twaindev wrote:

It is fixed.

Good Thanks for the feedback