Bug -> Could not find field [Active] on model [Watcher]

Lightspeed says

=> Could not find field [Active] on model [Watcher]

There is no such field on entity Watcher (and I am also not using it).

This is a large query which apparently is not accurately parsed by Lightspeed. I am using a field named active, but on three other tables.

I am expecting zero rows as there is no data in table BenchmarkDatas. Have converted it into a working SQL statement and am using it through a databaseprocedure now. S*cks ;-)

I know the query below is not easy to reproduce, but an error that reports fields on wrong entities might be a start.

var query = from w in uow.Watchers

                        where w.Id == WatcherDatabaseId
                        join p in uow.WatcherModuleParameterValues on w.Id equals p.WatcherId
                        join ws in uow.WatcherSecurities on w.Id equals ws.WatcherId
                        join scall in uow.Securities on ws.SecurityId equals scall.Id
                        join b in uow.BenchmarkDatas on ws.SecurityId equals b.SecurityId
                        join sput in uow.Securities on scall.Commodity equals sput.Commodity
                        join sunderlying in uow.Securities on scall.Commodity equals sunderlying.Commodity
                        where w.BenchmarkTypeId == b.BenchmarkTypeId
                        where scall.PutOrCall == "C"
                        where sput.PutOrCall == "P"
                        where sput.Strike == scall.Strike
                        where sput.ExpirationDate == scall.ExpirationDate
                        where sunderlying.InstrumentGroup == 5
                        where scall.InstrumentGroup != 5
                        where sput.InstrumentGroup != 5
                        where sunderlying.Active
                        where scall.Active
                        where sput.Active
                        select new { b, CallId = scall.Id, p, PutId = sput.Id, UlId = sunderlying.Id };

I believe I have reproduced this here with a local model and have added in a fix for the issue which will be available in the next nightly build. Let me know if this covers the issue you are seeing once you have had a chance to grab an updated nightly.

Jeremy