The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I've already rewritten my JSON engine a couple of times, and I've rewritten my TMDB api twice now. That last one made me want to drink. It's huge.
The first go round i guess was me getting the design straight. I needed to do it, so it wasn't a total loss. Massaging the data from TMDb gets ugly sometimes, so i needed something a bit more flexible on the second go, plus i happened on A Better Way(TM) in the process so that's happy.
Anyway, I love using Json to back the state in my entities. It's a joy to code against. Everything is easy, especially given the realm of data interchange
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Doing some testing on specific data meant I added one extra filter on the where clause saying basically "&& a.id == "A54321" - simple.
The query blew up because it referenced a field that was not yet defined in TEST (but was in DEV). My query didn't reference the field at all but somehow EF picked up that it needed to be ignored and referenced it so that it could ignore it(?) - causing the crash.
When I didn't add the extra filter the query worked fine. A friend suggested I should add the filter before the other parts of the where clause - so I did - and it worked!
Neither of us can understand why.
- I would love to change the world, but they won’t give me the source code.
Last Visit: 14-Nov-19 21:16 Last Update: 14-Nov-19 21:16