Duombaze.sql (2024)
Below is a complete draft for a generic system (e.g., a simple Content Management or Inventory system) that you can adapt. 1. Database Initialization
: Always use NOT NULL for required fields and UNIQUE for identifiers like emails to prevent duplicates. Duombaze.sql
: For passwords, never store them in plain text; use a VARCHAR(255) to accommodate hashed values. g., e-commerce, library, or medical records)? Below is a complete draft for a generic system (e
-- 2. Create 'Vartotojai' (Users) table CREATE TABLE vartotojai ( id INT AUTO_INCREMENT PRIMARY KEY, vardas VARCHAR(50) NOT NULL, pavarde VARCHAR(50) NOT NULL, el_pastas VARCHAR(100) UNIQUE NOT NULL, slaptazodis VARCHAR(255) NOT NULL, sukurta_data TIMESTAMP DEFAULT CURRENT_TIMESTAMP ); -- 3. Create 'Kategorijos' (Categories) table CREATE TABLE kategorijos ( id INT AUTO_INCREMENT PRIMARY KEY, pavadinimas VARCHAR(100) NOT NULL, aprasymas TEXT ); -- 4. Create 'Prekes' (Products) table with a Foreign Key CREATE TABLE prekes ( id INT AUTO_INCREMENT PRIMARY KEY, kategorija_id INT, pavadinimas VARCHAR(100) NOT NULL, kaina DECIMAL(10, 2) NOT NULL, kiekis INT DEFAULT 0, ar_aktyvus BOOLEAN DEFAULT TRUE, FOREIGN KEY (kategorija_id) REFERENCES kategorijos(id) ON DELETE SET NULL ); Use code with caution. Copied to clipboard 3. Data Population (Seed Data) Add initial "seed" data to verify the database structure. : For passwords, never store them in plain
Define your tables with primary keys, foreign keys, and constraints to ensure data integrity. Common tools like dbForge SQL Complete can help with advanced formatting and autocompletion of these T-SQL codes.
-- Select all products with their category names SELECT p.pavadinimas AS Preke, p.kaina, k.pavadinimas AS Kategorija FROM prekes p LEFT JOIN kategorijos k ON p.kategorija_id = k.id; -- Find products with low stock (less than 10) SELECT * FROM prekes WHERE kiekis < 10; Use code with caution. Copied to clipboard Best Practices for Your SQL Draft
To draft a complete duombaze.sql (Lithuanian for "database.sql"), a well-structured file should include the core elements for initializing a database: schema creation, table definitions with appropriate data types and constraints, and sample data for testing.