Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative way to handle patch string when it's too big to be stored as literal #202

Open
dlamoris opened this issue Feb 24, 2025 · 0 comments

Comments

@dlamoris
Copy link
Contributor

dlamoris commented Feb 24, 2025

In model load, there's insert/delete graph that can be used: can store the ins/del graph as commit metadata and let BranchWrite detect it/use it, or just always keep them and use this as the patch string instead (these graphs are currently not being deleted so they're just hanging around anyways - also add them as commit metadata so they can potentially be queried):

delete {
    graph ?__mms_model {
        ?s ?p ?o .
    }
} where {
    graph <delGraphIri> {
        ?s ?p ?o .
    }
};
insert {
    graph ?__mms_model {
        ?s ?p ?o .
    }
} where {
    graph <insGraphIri> {
        ?s ?p ?o .
    }
} 

Model commit (sparql update) also need an alternative

@dlamoris dlamoris added this to Flexo Feb 24, 2025
@github-project-automation github-project-automation bot moved this to New in Flexo Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

No branches or pull requests

1 participant