On math heavy queries what is the best way to handle titled? Was advised that other db systems would fail on a calculated field which obtains it's value from a calculated field defined in that query. So I'm not doing that. In an ideal world this makes it much easier but I will want to use MSSQL later.
To counter this I think a single class object (just a single predeclared class object which encapsulates all the math) may be better; retaining the parent's value in a property/ module-level variable (properties probably aren't even needed as everything actioned is within the class). The downside being sometimes I will run calculations which are not required; affecting performance.
What is my best route of action here?
On a sidenote - will passing the result returned from a function in a field of the query to another function bite me in the ass when converting to MSSQL?
- I have 30 calculated fields to determine relevant in this query (that's results; without fields in the query itself), & 15 variables.
To counter this I think a single class object (just a single predeclared class object which encapsulates all the math) may be better; retaining the parent's value in a property/ module-level variable (properties probably aren't even needed as everything actioned is within the class). The downside being sometimes I will run calculations which are not required; affecting performance.
What is my best route of action here?
On a sidenote - will passing the result returned from a function in a field of the query to another function bite me in the ass when converting to MSSQL?
Last edited: