panini-devs / bismarck Goto Github PK

Sup, @ROLFAN here!

In the end I will try to implement the wish simulator, so I need some information so I can know how to design the database.

Taking into account the following schema:

-- Wish Simulator Schema
CREATE TABLE IF NOT EXISTS wish_simulator (
    user_id BIGINT NOT NULL,
    entertwined_wishes INTEGER NOT NULL DEFAULT 0,
    limited_wishes_placeholder INTEGER NOT NULL DEFAULT 0, -- I forgor the name
    primos INTEGER NOT NULL DEFAULT 3200,
    standard_wishes_count INTEGER NOT NULL DEFAULT 0,
    limited_wishes_count INTEGER NOT NULL DEFAULT 0,
    character_list TEXT NOT NULL DEFAULT '[]',
    character_count INTEGER NOT NULL DEFAULT 0,
    weapon_list TEXT NOT NULL DEFAULT '[]',
    weapon_count INTEGER NOT NULL DEFAULT 0,
    PRIMARY KEY (user_id)
);

I guess that for each user it's desired to keep track of the amount of gacha roles, both in the standard wishes and the limeted ones (which I suppose are the event wishes), the characters they have got, and the weapons. However, I don't know what the purpose of the entertwined_wishes and primos entries are, it would be nice if someone could tell me.

In addition telling me which features should be implemented would be cool.

Thank you!

See SQLite Schema

User stored in DB must have:

1. Discord UID
2. Primogem amount (currency for wishing)
3. Event wishes amount
4. Standard wishes amount
5. A list of Character objects that they have obtained
6. A list of Weapon objects that they have obtained

Character object:

• name
• ID (positive integer)
• times obtained
• first obtained date (optional, can skip)
• rarity (enum of 4/5 star that can be converted into positive int of 4/5)

Weapon object:

• name
• ID (positive integer)
• times obtained
• first obtained date (optional, can skip)
• rarity (enum of 3/4/5 star that can be converted into positive int of 3/4/5)

Considering the lack of array support in SQLite, this would be difficult to implement. Change schema to fit PostgreSQL would be acceptable but doing this in SQLite is preferable as hosting a Postgres database is somewhat of a pain.

Currently chunks implementation to paginate warnings command to avoid embed character overflow.

Iterating through the chunk is an issue and this needs further work, currently stashing changes until a solution can be devised.