owncloud / owncloud/android

Remove SQLite database

Open
#4,203 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Contributions are welcome Technical
Dominant language
Kotlin
Stars
4.2k
Forks
3.1k
Avg merge
1d 12h
Merged PRs (30d)
7

Description

Time ago, Android app used to store data in SQLite DB. Then, new architecture came and everything was moved to Room.

But, SQLite exists still in the app

To do:

  • Check if something in SQLite DB is still used/useful
  • In case it is, migrate it to Room
  • Remove SQLite DB
TASKS
  • Research (if needed)
  • Create branch feature/feature_name
  • Development tasks
    • Implement whatever
    • ...
  • Code review and apply changes requested
  • Design test plan
  • QA
  • Merge branch feature/feature_name into master

Contributor guide

Open the contributing guide

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

Start by locating the Android app's remaining SQLite usage and the existing Room architecture. Determine whether any SQLite data is still useful, then identify the migration and removal scope. Done means required data is handled by Room and the obsolete SQLite database is removed, with appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin, sqlite
Domain
database, mobile
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.