Jarno Virta wrote:Yes. And as I said, just switching the place of one of the arguments at random, in both the SELECT query's NEW and the class' constructor arguments, fixes the problem. For that reason I was thinking might the query be cached somehow and maybe there was a change in datatype or something and maybe that might cause a problem with how the constructor call is made...? When I was poking around with this, just removing any of the arguments or adding an argument fixed the problem and switching back to the original argument list made the problem reappear. I also modified the database service method by removing the NEW call and I took the complete reports from the database, then looped through them and called the constructor for ReportQueryObject class for each report instance with the same exact properties as in the original query's argument list. That too worked without any problem. Weird...
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your databasehttps://coderanch.com/t/704633/RavenDB-Open-Source-NoSQL-Database