Scribd
Upload
4 views2 pages

BD Arena

The document outlines a database schema for a sales event system, detailing the structure of tables related to sales, events, users, categories, roles, sales details, tickets, collectives, and event types. Each table includes various fields with specified data types, such as BIGINT, INT, VARCHAR, and DECIMAL, to store relevant information. The schema supports relationships between entities like sales and events, as well as user and category information.

Uploaded by

David Velasco Ortega
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views2 pages

BD Arena

The document outlines a database schema for a sales event system, detailing the structure of tables related to sales, events, users, categories, roles, sales details, tickets, collectives, and event types. Each table includes various fields with specified data types, such as BIGINT, INT, VARCHAR, and DECIMAL, to store relevant information. The schema supports relationships between entities like sales and events, as well as user and category information.

Uploaded by

David Velasco Ortega
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

sales event user category

sales_id BIGINT 1 1 event_id INT 1 user_id INT 1 category_id SMALLINT

sales_quantity TINYINT event_name VARCHAR(255) user_email VARCHAR(100) category_name VARCHAR(100)

sales_date DATETIME event_description TEXT user_password VARCHAR(50) category_description VARCHAR(255)

sales_total_amount DECIMAL(8,2) event_additional_info TEXT user_register_date TIMESTAMP category_status BIT

payment_type_id TINYINT * event_url_poster CHAR(100) user_name VARCHAR(100)

event_id INT * event_datetime DATETIME user_surname VARCHAR(100)


payment_type
sales_detail_id BIGINT * event_like_counter INT user_birthdate DATE
1 payment_type_id TINYINT
event_status BIT user_genre ENUM(M,F,O)
payment_type_name VARCHAR(100)
event_url_site VARCHAR(100) user_country VARCHAR(50)
role
event_capacity TINYINT user_document_type ENUM(DNI,RUC)
role_id TINYINT 1
collective_id INT * user_document_number VARCHAR(11)
role_name VARCHAR(100)
category_id SMALLINT * user_photo_url VARCHAR(100)
role_description VARCHAR(250)
type_event_id TINYINT * user_collective_favorite VARCHAR(100)
* role_id TINYINT

sales_detail
ticket
sales_detail_id BIGINT 1
1 ticket_id INT ticket_type
quantity INT
ticket_description INT 1 ticket_type_id MEDIUMINT
sales_id BIGINT *
ticket_qr_unique_code VARCHAR(100) ticket_name VARCHAR(50)
ticket_id BIGINT *
event_id INT * ticket_capacity INT

ticket_type_id INT * ticket_price DECIMAL(10,2)

collective type_event

collective_id INT 1 1 type_event_id TINYINT

collective_name VARCHAR(100) type_event_name VARCHAR(100)

collective_category VARCHAR(30) type_event_description VARCHAR(250)

collective_country VARCHAR(50)

collective_city VARCHAR(100)

collective_district VARCHAR(69)

collective_address VARCHAR(255)

collective_email VARCHAR(255)

collective_description TEXT

collective_phone_number VARCHAR(20)
sales event user category

sales_id BIGINT 1 1 event_id INT 1 user_id INT 1 category_id SMALLINT

sales_quantity TINYINT event_name VARCHAR(255) user_email VARCHAR(100) category_name VARCHAR(100)

sales_date DATETIME event_description TEXT user_password VARCHAR(50) category_description VARCHAR(255)

sales_total_amount DECIMAL(8,2) event_additional_info TEXT user_register_date TIMESTAMP category_status BIT

payment_type_id TINYINT * event_url_poster CHAR(100) user_name VARCHAR(100)

event_id INT * event_datetime DATETIME user_surname VARCHAR(100)


payment_type
sales_detail_id BIGINT * event_like_counter INT user_birthdate DATE
1 payment_type_id TINYINT
event_status BIT user_genre ENUM(M,F,O)
payment_type_name VARCHAR(100)
event_url_site VARCHAR(100) user_country VARCHAR(50)
role
event_capacity TINYINT user_document_type ENUM(DNI,RUC)
role_id TINYINT 1
collective_id INT * user_document_number VARCHAR(11)
role_name VARCHAR(100)
category_id SMALLINT * user_photo_url VARCHAR(100)
role_description VARCHAR(250)
type_event_id TINYINT * user_collective_favorite VARCHAR(100)
* role_id TINYINT

sales_detail
ticket
sales_detail_id BIGINT 1
1 ticket_id INT ticket_type
quantity INT
ticket_description INT 1 ticket_type_id MEDIUMINT
sales_id BIGINT *
ticket_qr_unique_code VARCHAR(100) ticket_name VARCHAR(50)
ticket_id BIGINT *
event_id INT * ticket_capacity INT

ticket_type_id INT * ticket_price DECIMAL(10,2)

collective type_event

collective_id INT 1 1 type_event_id TINYINT

collective_name VARCHAR(100) type_event_name VARCHAR(100)

collective_category VARCHAR(30) type_event_description VARCHAR(250)

collective_country VARCHAR(50)

collective_city VARCHAR(100)

collective_district VARCHAR(69)

collective_address VARCHAR(255)

collective_email VARCHAR(255)

collective_description TEXT

collective_phone_number VARCHAR(20)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy