INCATools / semantic-sql

SQL and SQLite builds of OWL ontologies
https://incatools.github.io/semantic-sql/
BSD 3-Clause "New" or "Revised" License
37 stars 3 forks source link

Left over intermediate artefacts #47

Open joeflack4 opened 2 years ago

joeflack4 commented 2 years ago

Overview

I ran: semsql make doid.db, and these files remained afterwards:

  1. .template.db: Appears the CWD (current working directory) from where I'm running the command. It might be that this is because one of the commands failed, but I'm not sure.
  2. .template.db.tmp (edit: 2023/04/27: Also seeing these files; not sure which SemSQL version this started appearing in though.)
  3. doid-relation-graph.tsv.gz: Appears in the directory where my .db file is created, and the.owl file used to create that file is located.

Replicating this issue

  1. Have semsql
  2. Download and unzip doid.owl.zip
  3. Run semsql make doid.db from unzipped directory, or use the dockerized version.
joeflack4 commented 2 years ago

@matentzn FYI

joeflack4 commented 1 year ago

i think i'm only still experiencing left over .template.db. But it may be because a script is not completing successfully. or perhaps it does it every time, I'm not sure.

matentzn commented 1 year ago

@hrshdhgd what do you think regarding this issue?

hrshdhgd commented 1 year ago

.template.db: Appears the CWD (current working directory) from where I'm running the command. It might be that this is because one of the commands failed, but I'm not sure.

.template.db is an intermediary file that gets generated each time semsql makes a .db file. It remains after successful db file generation

doid-relation-graph.tsv.gz: Appears in the directory where my .db file is created, and the.owl file used to create that file is located.

This again is relation-graph generating the tsv file which eventually gets converted to the sqlite db file

@joeflack4 , why can't you get the latest version of semsql installed?

joeflack4 commented 1 year ago

That was a while ago. I have it so that semsql works inside and outside of Docker on my machine now, but I usually use the dockerized version since it's been easier to keep up-to-date. I edited out the version related information from the top of the issue.