Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Artifact ID: | a3d64bb8ef4c0601800819556f8f37421d18ad78bcd6e5c9a35a6d49f002086c |
---|---|
Page Name: | Star Trek Database |
Date: | 2025-03-30 01:20:55 |
Original User: | chungy |
Mimetype: | text/x-markdown |
Parent: | c7269fb53567731c055121248825f86472368ccf9a197d8e40f63d82b4cd2fb0 (diff) |
Next | cfa8ab29f6d8902c71fee392e2bbb8ca671f39d78addd4021e73672e4e1aa2a9 |
Star Trek database
This is a database containing metadata for all the episodes and movies in the Star Trek franchise. It can be used to query information about episode listings, DVD and Blu-ray contents, release dates, star dates, and a few other miscellany. The database covers all fourteen movies released, and classic Star Trek television episodes (this is to say, everything through the end of Star Trek: Enterprise). One additional, and unofficial, entry is Star Trek Continues, because I am a fan of this fan-made series.
This database is built in SQLite, a portable and no-install database program contained in a single program, and the database in a single file. This makes it easy to use without any sort of database administration required.
Using the database
A pre-built binary database may be downloaded from the following link: startrek.db. You can use sqlite3 startrek.db
to interact with the database, or any number of available SQLite-compatible GUI utilities.
The source code to this project is primarily two files: schema.sql
and data.sql
. In a fresh check-out of the repository, you may run
$ make
to build the startrek.db
file, which should be practically identical to the above download, barring trivial differences between SQLite versions. Both a Makefile (for Unix systems) and Windows batch file are provided; as long as you have sqlite3
in your $PATH
, it should work.
Cloning the repository
This is a Fossil repository, and may be cloned (having fossil
in your $PATH
) by:
$ fossil clone https://chiselapp.com/user/chungy/repository/startrek-db
Future plans
Without any promise for plans to be realized (this project is 10 years old at time of writing), some ideas:
Expanded media
The media set tables are biased toward media that I actually own. Star Trek has been on virtually every kind of physical media that has ever existed (LaserDisc, Betamax, VHS, etc), and there remains a lot of room to document all of it.
Kurtzman-era documenation
As mentioned earlier, only classic Star Trek is represented. In the earlier PostgreSQL version of the database, I had kept updates for Discovery, Lower Decks, and Picard, but apathy toward the Alex Kurtzman era caused me to become disinterested and I never stuck with them to the end of their runs, and likewise did not update the PostgreSQL database as episodes came out. I'll use the Postgres version to reference what's in there, and siphon Memory Alpha for the rest.
GUI/WebUI to interact with the database
SQL is not for everyone. It may be nice to make a GUI program or a WebUI to interact with the database.