Add default ancestry format and primary key format #612
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
These tend to be the same across a whole database. The primary key format is used for databases with uuids for the primary key The ancestry format makes it easy for a new user to get up and running using a different ancestry encoding format
|
@kshnurov do you know how to use I feel this is probably the easiest way to get users up and running using the new materialized path2. |
|
if you have an answer, we can circle back later. I want to get this merged, so I can use it in documenting ancestry collation and get us closer to a gem release |
kbrock
added a commit
to kbrock/ancestry
that referenced
this pull request
Mar 3, 2023
* Fix: descendants ancestry is now updated in after_update callbacks stefankroes#589 * Document updated grammar stefankroes#594 * Documented `update_strategy` stefankroes#588 * Fix: fixed has_parent? when non-default primary id stefankroes#585 * Documented column collation and testing stefankroes#601 stefankroes#607 * Added initializer with default_ancestry_format stefankroes#612 * ruby 3.2 support stefankroes#596
kbrock
added a commit
to kbrock/ancestry
that referenced
this pull request
Mar 3, 2023
* Fix: materialized_path2 strategy stefankroes#597 * Fix: descendants ancestry is now updated in after_update callbacks stefankroes#589 * Document updated grammar stefankroes#594 * Documented `update_strategy` stefankroes#588 * Fix: fixed has_parent? when non-default primary id stefankroes#585 * Documented column collation and testing stefankroes#601 stefankroes#607 * Added initializer with default_ancestry_format stefankroes#612 * ruby 3.2 support stefankroes#596
|
You're instantly merging things left and right without even thinking and reviewing. What the hell is going on? |
|
I wanted to simplify our readme and this made it easier. |
This was referenced Mar 4, 2023
kbrock
added a commit
to kbrock/ancestry
that referenced
this pull request
Mar 4, 2023
* Fix: materialized_path2 strategy stefankroes#597 * Fix: descendants ancestry is now updated in after_update callbacks stefankroes#589 * Document updated grammar stefankroes#594 * Documented `update_strategy` stefankroes#588 * Fix: fixed has_parent? when non-default primary id stefankroes#585 * Documented column collation and testing stefankroes#601 stefankroes#607 * Added initializer with default_ancestry_format stefankroes#612 * ruby 3.2 support stefankroes#596
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.
These tend to be the same across a whole database.
The primary key format is used for databases with uuids for the primary key The ancestry format makes it easy for a new user to get up and running using a different ancestry encoding format