Cline rules

1# SQLite Data Modeling Guidelines for GraphQL Filter Demo
2 
3This document outlines the guidelines for data modeling using SQLite for the GraphQL Filter Demo project, focusing on the data warehouse structure.
4 
5## Adherence to DW Schema
6 
7*   Strictly follow the defined data warehouse schema with a central fact table (`FatoVisitas`) and associated dimension tables.
8*   Ensure correct relationships and foreign keys are defined in the schema.
9 
10## SQLite Data Types
11 
12*   Use appropriate SQLite data types for each column (e.g., `INTEGER` for IDs and counts, `TEXT` for strings, `REAL` for floating-point numbers, `BLOB` for binary data, `INTEGER` for timestamps or dates stored as Unix time).
13*   Be mindful of SQLite's flexible typing but aim for consistency.
14 
15## Primary and Foreign Keys
16 
17*   Define primary keys (`PRIMARY KEY`) for all tables.
18*   Define foreign keys (`FOREIGN KEY`) to enforce relationships between the fact and dimension tables.
19*   Consider using `INTEGER PRIMARY KEY` which is an alias for `ROWID` and can offer performance benefits.
20 
21## Indexing
22 
23*   Create indexes on columns frequently used in `WHERE` clauses or `JOIN` conditions, especially foreign key columns in the fact table.
24*   Analyze query patterns to identify columns that would benefit from indexing.
25 
26## Normalization
27 
28*   Maintain a normalized structure for dimension tables to avoid data redundancy.
29*   The fact table will naturally have foreign keys referencing the dimensions.
30 
31## Data Integrity
32 
33*   Utilize constraints (e.g., `NOT NULL`, `UNIQUE`) to ensure data integrity where appropriate.
34