astrodbtoolkit / astrodbtoolkit/AstrodbKit

Think about filename extensions

Open
#62 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
12
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I noticed that for SIMPLE, we have an SQLite database but we end up with .db file. Should we consider using the .sqlite or .sqlite3 extension when the output file is an SQLlite database?

Relevant SO discussion: https://stackoverflow.com/questions/808499/does-it-matter-what-extension-is-used-for-sqlite-database-files

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names SIMPLE's SQLite output but no source file or test. Start by locating where the output filename is chosen, then inspect the existing SQLite-output behavior; done means the project uses the agreed extension consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sqlite
Domain
databases
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.