XD-1198 filter entity types #257
Closed
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
XD-1065: Soften class name check for OQueryFunctions
…delete-links-with-indices
Delete links with indices
Update unwrap in sort
A transaction is active/usable from our point of view only if it is in a BEGUN state
It seems that we should always use rollback(force = true), otherwise the session may get a broken state and become unusable.
The previous implementation created a session on every access to the sequence (get, increment, etc.) The new implementation creates a new session only when both the sequence has not been created yet and the current session has an active transaction. Also, the new implementation makes sure that the sequence is created right away and not lazily.
…that creates sessions It leaves less room for bugs because the client's code does not have to deal with closing the new session and reactivating the previous one.
XD-1065: Use named query parameters
Graph store restore in memory
1. The transaction lifecycle is tightly bound to the ODatabaseSession lifecycle. Transactions start and finish with sessions. 2. Transaction can be read-only. 3. Transactions validate their state on every operation. 4. OEntityStore does not let create several transactions on a single thread. 5. Get rid of the code for nested/embedded transactions
Graph store xd 1116
…y-renew # Conflicts: # entity-store/build.gradle.kts
Reimplementation of resetToNew method - second attempt.
XD-1180 updated patterns for (re)move old database
YTDB upgrade.
YTDB upgrade. p2.
Bug in exclude was fixed.
…tation dependency from migration.
…tity-store Extracted persistentEntityStore code to separate module with implemen…
Move more packages
Fixed empty iterable operations
…ead-only XD-1195 propagated read-only mode flag to the store
YTDB-248 Removed OSystem folder
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.
What does this PR do?
Filter out edge class names and vertex internal class names
Motivation
What inspired you to submit this pull request?
Related issues
A list of issues either fixed, containing architectural discussions, otherwise relevant
for this Pull Request.
Additional Notes
Anything else we should know when reviewing?
Checklist
[x] I have added unit tests to the code I am submitting
[x] My unit tests cover both failure and success scenarios
[] If applicable, I have discussed my architecture