Support Forum

[victor]

Hello,

I dont know, maybe you are thinking about it before now:

After I have tried to generate a specific subtask lists or report I have needed to use an SQL query to get it and I am thinking that maybe a very customizable method to generate reports (and maybe define filters) could be ginving a SQL expression.

I dont know if this is hard to implement but for the future this solution could give you a last choice to specific user needs.

[admin]

Hello,

I dont know, maybe you are thinking about it before now:

After I have tried to generate a specific subtask lists or report I have needed to use an SQL query to get it and I am thinking that maybe a very customizable method to generate reports (and maybe define filters) could be ginving a SQL expression.

I dont know if this is hard to implement but for the future this solution could give you a last choice to specific user needs.

Sorry, but we don't use SQL to get tasks - we filter task in-memory using Java code. Early TrackStudio versions was use SQL, but we remove that cause because low perfomance and high complexity.

PS. You can use calculated custom fields for complex conditions.

[victor]

Sorry, but we don't use SQL to get tasks - we filter task in-memory using Java code. Early TrackStudio versions was use SQL, but we remove that cause because low perfomance and high complexity.

PS. You can use calculated custom fields for complex conditions.

Oh, I understand. Expand calculated custom maybe then could be the way... By the way, are the calculated custom fields values stored in the database?

Thanks

[admin]

Sorry, but we don't use SQL to get tasks - we filter task in-memory using Java code. Early TrackStudio versions was use SQL, but we remove that cause because low perfomance and high complexity.

PS. You can use calculated custom fields for complex conditions.

Oh, I understand. Expand calculated custom maybe then could be the way... By the way, are the calculated custom fields values stored in the database?

Thanks

No, they are calculated when required.

PS. You can learn more about calculated field syntax (very similar to Java) here: http://www.beanshell.org/manual/contents.html

[victor]

No, they are calculated when required.

Great!,

PS. You can learn more about calculated field syntax (very similar to Java) here: http://www.beanshell.org/manual/contents.html

Fine, thanks!... Pitifully I need ask about parent and grandparent tasks and currently this is not possible with calculated fields.

Thanks

[admin]

Fine, thanks!... Pitifully I need ask about parent and grandparent tasks and currently this is not possible with calculated fields.

Thanks

Yes, this is because in current architecture its difficult to test can you access parent task or not. But we'll fix this problem in next version (and will implement more comprehensive object model).

[victor]

Yes, this is because in current architecture its difficult to test can you access parent task or not. But we'll fix this problem in next version (and will implement more comprehensive object model).

Nice news, I am beginnig to love calculated custom fields ;)

Thanks