Constant max value

RE: Constant max value

davids0001 — Mon, 14 Aug 2017 18:44:39 GMT

One rule of thumb that I like to utilize constants in place of reference tables with data that won't be frequently changed. This isn't transaction data you expect to change daily but lookup values that might not change for a year or more. A list of US States would be perfect as a constant and not DB.

If it has more than 100 or 200 rows, or if each row has more than 5 or 6 elements you might want to consider a DB query rather than constant. After a certain size the speed of SQL makes up for the delay in linking to it.

RE: Constant max value

naveenp878 — Mon, 14 Aug 2017 18:27:18 GMT

Hi - I agree with both views with little correction. As sravanis said, There is no limit to the values of a constant type and issue with memory. Memory with the constants or rules can happen only when the versions are in more. Example if the constant has 200 version then it will use steap memory.

We have a situation where one of the constant has 10,000 version which was updating at a specific interval with makes the system completey unusable. Then we had to delete the version to restore it back.

So as suggested by kchaitanyam, the best practice is used go for a database table and on demand you fetch the required data as when needed.

RE: Constant max value

sravanis — Mon, 07 Aug 2017 06:24:21 GMT

Hi ashokv,

As per my knowledge, there is no limit for constant to hold values.

thanks,
Sravani.

RE: Constant max value

Krishna Chaitanya — Mon, 07 Aug 2017 05:37:11 GMT

No limit, but it will increase the memory usage,so better to go with database.
plz correct me if am wrong.