Open GoogleCodeExporter opened 9 years ago
Just so we're clear, we're talking about something like:
CREATE TABLE [foo].[Names] (ID INTEGER, Name VARCHAR(20));
CREATE TABLE [foo].[Employees] (ID INTEGER, NameID INTEGER NULL,
CONSTRAINT "FK_Employees_Name" FOREIGN KEY ("NameID") REFERENCES
[foo].[Names] ("ID")
);
CREATE TABLE [bar].[Names] (ID INTEGER, Name VARCHAR(20));
CREATE TABLE [bar].[Employees] (ID INTEGER, NameID INTEGER NULL,
CONSTRAINT "FK_Employees_Name" FOREIGN KEY ("NameID") REFERENCES
[bar].[Names] ("ID")
);
i.e. we have e.g. two identically named tables in different schemas which have
a
foreign key relationship (within or across schemas).
It looks like supporting this will require changing DbLinq.Schema.Dbml.Table to
include the Schema name (in addition to the name) so that
DbmlExtensions.GetReverseAssociation() doesn't find the wrong column.
Original comment by jonmpr...@gmail.com
on 11 Mar 2010 at 7:01
Original issue reported on code.google.com by
outlanderzor
on 23 Feb 2010 at 2:14