You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
user logs in
fetch their wallet address
check if the address already exists in db
if it doesn't exist, create a new record
if it does exist, retrieve the users projects
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.
The text was updated successfully, but these errors were encountered:
shrnkld
changed the title
Design the database structure for storing users data
Design and implement the database structure for storing users data
Dec 22, 2022
shrnkld
changed the title
Design and implement the database structure for storing users data
Design and implement the database for storing users data
Dec 22, 2022
shrnkld
changed the title
Design and implement the database for storing users data
Design and implement a database to store users data
Dec 22, 2022
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:
Implement an SQLite database
To do:
Projects:
-- project_ID (primary key)
-- user_ID
-- API_key
-- project_created_date
Users:
-- user_ID
-- wallet_address
-- user_created_date
User flow:
user logs in
fetch their wallet address
check if the address already exists in db
if it doesn't exist, create a new record
if it does exist, retrieve the users projects
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.
The text was updated successfully, but these errors were encountered: