nmluci / stellarcoffee Goto Github PK

As an engineer, I want to be able to retrieve all or some order based the criteria I give, so I can get a precise list of what to get

As an engineer, I want to have a connection to the database, so I can exchange data

as a backend engineer, I want to listen HTTP Request so I can process the request

Acceptance Criteria:

• has a persistent route
• being able to listen to HTTP Request

As an engineer, I want Inventory to have its own separated module, and some class based on the type of object it holds, so I can access anything related to Inventory from its own class

Acceptance Criteria:

• being a separated module
• accessible from the rest of the project
• being a precise and separate object

As an engineer, I want to have a separate class for Customer and Member, so each type of object can only do certain stuff

As a user, I want to retrieve a Item from the Inventory, so I don't need to access it directly from the database

As a engineer, I want to update member's data, so I don't need to delete and insert a new data when a member's data changed

As a engineer, I want an easy way to add a customer as a member (membership), so I don't need to interact directly with the database to do it

As an engineer, I want an easy way to remove a customer from a membership, so I don't need to interact directly with the database to do it

As an engineer, I want to give a consistent payload on Success Response, so a consistent payload can be sent on each request

As an engineer, I want to give a consistent payload on Failed Response, so a consistent payload can be sent on each request

When i want to run the backend, errors appear

sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1005, 'Can\'t create table `stellarCoffee`.`Events` (errno: 150 "Foreign key constraint is incorrectly formed")')   
CREATE TABLE Events (
        id INTEGER NOT NULL AUTO_INCREMENT,
        name TEXT,
        item_name TEXT,
        date_end DATE NOT NULL,
        amount INTEGER NOT NULL,
        amount_type TEXT NOT NULL,
        PRIMARY KEY (id),
        UNIQUE (id),
        UNIQUE (name),
        FOREIGN KEY(item_name) REFERENCES Inventory (name) ON DELETE SET NULL ON UPDATE CASCADE
)

I think that error tells us to create the right order for migrating DB. I don't know how to create the right order, sad :(

As an engineer, I want to be able to do an operation to database, and do all action related to the database through a function, so other module don't need to directly access the database

as an engineer, I want to add item to inventory using its separate class, so I don't need to interact with the database directly

As a engineer, I want to remove an Item from Inventory using its own class, so I don't need to delete it directly from the database

As a engineer, I want to be able to update an order, so there will be no duplication of order

As an user, I want to update an item from Inventory Instance, so I don't have to update it directly from the database

As a engineer, I want to get a list of member of our shop, so I can check if a customer also a member

As an engineer, I want to be able to cancel an order, so I know which order is cancelled, and which order is done

As an engineer, I want to be able to insert a new order, so I don't need to send the data to each module

As an engineer, I want Ordering has its separate class, so all thing related to it, can only be done through its instance alone

As an engineer, I want to have a way to interact the database indirectly, so all of the action to the database can be checked before executed