Skip to content

Documentation for DATEPARSE#11010

Open
dahfjkg wants to merge 2 commits intomendix:developmentfrom
dahfjkg:dat/dateparse
Open

Documentation for DATEPARSE#11010
dahfjkg wants to merge 2 commits intomendix:developmentfrom
dahfjkg:dat/dateparse

Conversation

@dahfjkg
Copy link
Copy Markdown
Contributor

@dahfjkg dahfjkg commented Apr 10, 2026

Requires team review. To be published with Studio Pro 11.10

@MarkvanMents
Copy link
Copy Markdown
Collaborator

I'll pick this up once the technical review has been passed.

@pijuskri
Copy link
Copy Markdown
Contributor

Approved by Team for technical review

Copy link
Copy Markdown
Collaborator

@MarkvanMents MarkvanMents left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dahfjkg
Thanks for the PR Pavel. I have made one minor suggestion - let me know if you think it is an improvement or non needed?

Comment on lines +1056 to +1057
1. HSQLDB accepts values `0` to `11`
2. Other databases accept values `1` to `12`
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we actually use zero-based and one-based in this description to make it easier to see the difference?

Suggested change
1. HSQLDB accepts values `0` to `11`
2. Other databases accept values `1` to `12`
1. HSQLDB uses zero-based indexing and accepts values `0` to `11`
2. Other databases use one-based indexing and accept values `1` to `12`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants