docs: EXPOSED-499 Add examples of custom data types #2213
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was
linked to
issues
Aug 23, 2024
e5l
approved these changes
Aug 26, 2024
|
|
||
| ### Ltree type | ||
|
|
||
| PostgreSQL provides a data type, `ltree`, to represent hierarchical tree-like data. |
There was a problem hiding this comment.
would be nice to have url to the postgre docs here
vnikolova
reviewed
Aug 26, 2024
| The following examples describe different ways to customize a column type, register a column with the custom type, | ||
| and then start using it in transactions. | ||
|
|
||
| ### Ltree type |
There was a problem hiding this comment.
I suggest to omit "type" from the titles and use the descriptive names. So instead of "Ltree type" this would be "Hierarchical tree-like data".
Add a new section to 'Data Types' page with examples of how to implement different custom types
- Add external reference links for each database type - Change subsection titles to be more descriptive
bog-walk
force-pushed
the
bog-walk/docs-custom-data-type
branch
from
891496d
to
2cc8367
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Summary of the change:
Adds a new section to 'Data Types' page with examples of how to implement different custom types.
Detailed description:
Why:
Their implementation and maintenance as out-of-the-box Exposed types is very low priority given their scope of support.
What:
ltree,YEAR,int4range | daterange,SET,hstore,citext) and how to use them.Type of Change
Please mark the relevant options with an "X":
Affected databases:
Checklist
Related Issues
EXPOSED-499
EXPOSED-500