Jump to content

Performance: stored calculation field vs auto-enter calculation field


This topic is 2596 days old. Please don't post here. Open a new topic instead.

Recommended Posts

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!

Link to comment
Share on other sites

This topic is 2596 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.