Last post Sep 20, 2016 05:07 PM by PatriceSc
Sep 15, 2016 12:31 PM|tvb2727|LINK
I am seeing an issue where I am trying to dot into a relationship, but the relationship is coming back NULL when the natural key is different on one table compared to the other table.
The primary key is a natural key etc.
Table 1 USER: has the user name as: JOE_SMITH
Table 2 OTHER_TABLE: has the user name as: JOE_sMITH
If the user name is JOE_SMITH in both tables, then the relationship from the USER table will come back
If the user name is JOE_sMITH in the non user table, then it will not bring back the relationship from the USER.
Let me know if this make sense and why Entity is not bring back the relationship that we try to dot into when the casing is different.
Sep 16, 2016 05:54 AM|meeyourmark|LINK
what is the relationship you are creating ?
Sep 17, 2016 09:54 AM|PatriceSc|LINK
Check the db side table definition. More likely you are using case sensitive columns.
https://msdn.microsoft.com/en-us/library/ms180175(v=sql.105).aspx if using SQL Server ("SQL Server Collation Name")
Sep 19, 2016 01:53 PM|tvb2727|LINK
*** Please Ignore... posted on wrong post.
Sep 19, 2016 02:52 PM|PatriceSc|LINK
Great but it seems unrelated to the issue you had. For now it seems you are using a local database that is not case sensitive and another database on some remote server which is case sensitive.
Being local or not is absolutely unrelated to being case sensitive or not.
Sep 20, 2016 05:07 PM|PatriceSc|LINK
And so have you checked that the columns used on the database side are case insensitive? IMHO they are case sensitive causing this issue.