This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am having a problem that I am unable to trace the routes of, I have examined the SQL sent to the server, amd it is obvioulsy in error, but I cannot see why. The LINQ expression is as follows:
var op = uow.FindOne<OperatorDef>(Entity.Attribute("OperatorId") == operatorID);
var srs = from sr in uow.SystemReports The SQL this creates is like this:
SELECT SELECT SystemReportsParameter.Id,
From this, the first SQL statements actions correctly, the second onw produce the error below:
The multi-part identifier "t2.DatabaseId" could not be bound. The multi-part identifier "t2.AccessLevel" could not be bound. The multi-part identifier "t2.DataAccessGroup" could not be bound. I would be grateful for any help here, from my limited knowledge, I think the LINQ statement is correct. Many thanks your you help with this. PS. The Database server is SQL Server 2005. |
|
|
Hi Mark, This looks fine and it would appear that the issue is in the joined table (t2) not being automatically joined in the eager load query (second select statement). Are you running the latest nightly build? If you are, would you able to provide a small repro sample for this behavior and we will be able to have a look into this?
Jeremy |
|
|
Hi Jeremy, I am not using any of the nightly builds, I am using the last full release. I noticed the warnings on the nightly build page, and decided it was safer to still with the full release version. I will download the latest nightly build, and see if it fixes the problem. Thanks |
|
|
Hi Mark, I would strongly suggest grabbing the latest nightly build. There have been quite a lot of fixes since RTM and I suspect this would be covered by them. Let us know if that is not the case though!
Jeremy |
|
|
Just to let you know I downloaded the latest nightly build and it fixed this problem. Thanks for that. Is there any information available of what is new and improved etc. in the nightly builds? Or what is different from the last full release?
|
|