Performance: stored calculation field vs auto-enter calculation field

[TJ53]

Is there any difference in terms of performance between a calculation field (stored and indexed) and field defined as auto-enter calculated value (indexed)?

For example, we have an “INVOICE” table, with a field called “date_invoice_sent”, and we’d like to have a boolean field called “is_sent”.

The calculation would be “not IsEmpty(date_invoice_sent)”

So we have two options here:

- Calculation field (stored, number result).
- Number field defined as “auto-enter / calculated value / do not replace … unchecked”.

Would there be any difference in performance between the two options? thanks in advance!

[Wim Decorte]

No difference AFAIK.

[TJ53]

2 hours ago, Wim Decorte said:

No difference AFAIK.

Thank you!

[comment]

See also:
https://community.filemaker.com/message/276855#276854

 

 

Edited February 18, 2017 by comment

[TJ53]

48 minutes ago, comment said:

See also:
https://community.filemaker.com/message/276855#276854

 

 

Excellent, thank you!