Skip to content

Design and implement a database to store users data #41

@sh-rn

Description

@sh-rn

Scenario:

If a user logs in to the dashboard, when they have an active, inactive, or pending project, then we will display those projects in the table component.

What we need:
A back-end database that can act as the storage mechanism for the user data.

Database structure:
See comment below...

To do:

  • define the database structure and data needed

Implement an SQLite database

To do:

  • implement the database using SQLite
  • store the following data:
    Projects:
    -- project_ID (primary key)
    -- user_ID
    -- API_key
    -- project_created_date
    Users:
    -- user_ID
    -- wallet_address
    -- user_created_date

User flow:

  1. user logs in

  2. fetch their wallet address

  3. check if the address already exists in db

  4. if it doesn't exist, create a new record

  5. if it does exist, retrieve the users projects

  6. when a user creates a new project, search for an existing user. If no user is found > go to 4. If the user is found > go to 5 and append new project info.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

Status
QA

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions