Open-event-server: Clarify DB tables

[iamareebjamal]

Some table's roles are unclear.

• [ ] roles_panels - contains 1000s of duplicate entries
• [ ] transaction - why are these in the database?
• [ ] mails - Why are these in the database? They consume 20% of production DB
• [ ] events_version - stores redundant versions where nothing is changed between rows
• [ ] orders_tickets - redundant table. Remove and use redis for caching if needed

[kushthedude]

• mails - Why are these in the database? They consume 20% of production DB

This takes a record of each & every mail which is sent from the app to the users. And details regarding those are then displayed in Admin/Mails

[iamareebjamal]

I know what it is used for, but why?

[mrsaicharan1]

@iamareebjamal For orders_tickets, how exactly is redis caching going to be useful?

[iamareebjamal]

If you need to cache the amount of tickets associated with the order, cache it rather than storing it in a separate table in DB. It's the violation of single source of truth and source of bugs

[mrsaicharan1]

The number of tickets associated with orders is being used everywhere in the application. Okay, I get your point.
But what I'm still skeptical about is the reason why the quantity field wasn't present in the orders table from before

[mrsaicharan1]

Nvm, it's there

[iamareebjamal]

SELECT count(*) from ticket_holder where order_id = 5;

[EkanshMangal]

Hello Sir,
If issue is not solved, Can i try to solve it

[iamareebjamal]

Not meant for beginners, please don't spam comment on issues