With clause and column matching

[Tim Bourguignon]

Hi everyone,

I cannot manage to wrap my head around this one.

I have two SQL tables "EntityValues" and "PropertyValue".

The "PropertyValue" table has two columns containing foreign keys to the "EntityValues" but with different meanings: 

• PropertyValue.EntityValue means that the entity has a property (inverse relation)
• PropertyValue.ReferencedEntityValue means that the property actually references another entity
  

When I try a very broad query like the following, Simple.Data joins the data using the ReferencedEntityValue column and not the EntityValue as I would like it to:

> db.EntityValues.All().With(db.PropertyValues)

Do you have any hints on how to solve this?

Thanks,

Tim

[Mark Rendle]

Simple.Data will follow the referential integrity in the DB. You can use an explicit join to override this.

See the bottom of this page for an example: http://simplefx.org/simpledata/docs/pages/Retrieve/EagerLoadingJoins.htm

Cheers,

Mark

Mark Rendle

Founder & CEO

Oort Corporation

Makers of Zudio

--
You received this message because you are subscribed to the Google Groups "Simple.Data" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simpledata+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Tim Bourguignon]

Hi Mark, thanks for your answer!

I might be misunderstanding the concept of referential integrity then because that's exactly what I expected.

The two columns in the PropertyValue table contain foreign keys, but one column is nullable and the other one is not. The one that Simple.Data is automagically taking is the nullable one... doesn't that go against the referential integrity?

Thanks,

Tim

[Mark Rendle]

Ah. Simple.Data will just take the first key it finds, so the nullable one is obviously bring returned first.

[Tim Bourguignon]

Damn. I'll go the explicit joins way then ;)

Thanks a bunch!