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

Automatic filenaming on branched graphs. #232

Open
white-gecko opened this issue Apr 30, 2019 · 0 comments
Open

Automatic filenaming on branched graphs. #232

white-gecko opened this issue Apr 30, 2019 · 0 comments

Comments

@white-gecko
Copy link
Member

white-gecko commented Apr 30, 2019

  1. Start quit on an new repo.

    content = "<http://ex.org/a> <http://ex.org/b> <http://ex.org/c> ."
    with TemporaryRepositoryFactory().withGraph("http://example.org/", content) as repo:
        args = quitApp.parseArgs(['-t', repo.workdir])
        objects = quitApp.initialize(args)
        config = objects['config']
        app = create_app(config).test_client()
    
  2. Create two branches from the same original branch

        app.post("/branch", data={"oldbranch": "master", "newbranch": "develop"})
        app.post("/branch", data={"oldbranch": "master", "newbranch": "target"})
    
  3. Insert data into the same new graph on both branches.

        update = "INSERT DATA {graph <http://new.org/> {<http://ex.org/x> <http://ex.org/y> <http://ex.org/z> .}}"
        app.post('/sparql/target', data={"update": update})
    
        update = "INSERT DATA {graph <http://new.org/> {<http://ex.org/z> <http://ex.org/y> <http://ex.org/x> .}}"
        app.post('/sparql/develop', data={"update": update})
    

Problem: in one branch there will be new.nt and in the other one new_1.nt.
Further there is a problem merging the two graphs from different files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant