Fix DB_RESULT_LIMIT Parsing to Allow Integer Configuration

[TeachMeTW]

Summary

Fixes an issue where the DB_RESULT_LIMIT configuration was being treated as a string, preventing it from being set as an integer dynamically. The update ensures the value is properly parsed as an integer, enabling correct configuration usage.

Changes

• Ensures DB_RESULT_LIMIT is parsed as an integer.
• Retains the default value of 250000 if the configuration is not explicitly set.

Why This Fix?

• Previously, the value of DB_RESULT_LIMIT was treated as a string, leading to unexpected behavior when attempting to use or override it.
• This change resolves the type mismatch and ensures the value can be correctly parsed and used as an integer.

Testing

• Tested with no DB_RESULT_LIMIT set: defaults to 250000.
• Tested with DB_RESULT_LIMIT set to a valid integer: properly reflects the configured value.
• Tested with invalid DB_RESULT_LIMIT (non-numeric string): verified that it raises an appropriate error -- defaults to 250,000 if error