How the odb works in Atlantis

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
sqlite
Domain
databases, documentation

Research direction

No file, test, or entry point is named; start with the issue text’s description of Atlantis, Berkeley, SQLite, and guest databases. Done is not defined because the issue does not request a specific change or provide a verification target.

Written by the indexing model from the issue text.

Description

Atlantis is the codename for the version of Frontier I'm working on with Claude.

The OPML Editor version I'm using from 2014 is called Berkeley.

Atlantis uses SQLite to store all its data.

There is no official frontier.root, though you will be able to export the non-guest-database content from the SQL into a file that's totally consistent with the Berkeley database, in fact you can open it in Berkeley and it works.

When you install a guest database, by simply putting it in the tools folder (same as in Berkeley). When Atlantis starts up it loads the content into the SQL database. As with frontier.root, you can export it.

I haven't tested all this yet, but today I'm going to install my first guest database this way.

Dominant language
No language data
Stars
0
Forks
0
No merged PRs in 30d

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.

More from scripting/helloFrontier

All issues in scripting/helloFrontier

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.