FIR-28289 Change SUBSTRING's <start> and <count> parameters to BIGINT

[zlifb]

PackDB PR: https://github.com/firebolt-analytics/packdb/pull/8531 .

We used to define the signature of substring function following PostgreSQL, which has <start> and <count> parameters defined as INTEGER. Calling substring with BIGINT values for these parameters fail in PostgreSQL, and we kept the same behavior.

However, we agreed that this is not very convenient. Supporting BIGINT types for these parameters should be a natural extension. It does not hurt our "PostgreSQL compliant" claim. In addition, given that we still produce BIGINT for arithmetic addition of integers, this is just convenient for our user to make in-position call to other functions.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[molly-firebolt]

Thank you for the PR @zlifb - is this behavior already live, or do we need to wait for a release version to be tagged on the ticket?

[zlifb]

@molly-firebolt The change is merged in master, but not included in the 3.30 release. So it will be in for 3.31 I assume. I tried to tag the Jira ticket but there seems to be no packdb-3.31 yet.