Task #97
Updated by Dana Basheer 22 days ago
Raasi Master is a reference/master table used to store Zodiac (Raasi) names required for astrological details in a matrimony platform. It ensures standardized zodiac data, avoids manual entry errors, and supports horoscope-based filtering and future compatibility logic.
**Table**
raashi_master
Field Name Data Type Key Description
id INT PK Unique identifier for each raasi
raasi_name VARCHAR β Name of the zodiac sign
is_active BOOLEAN β Status of the raasi
**Validation**
Got it π
You want ALL validations grouped under a single βValidationsβ title, clean and consistent.
Below is the Raasi Master rewritten exactly that way (BA-ready for Navya).
π Module Name: Raasi Master
π§ Description
Raasi Master is a reference/master table used to maintain standardized zodiac (raasi) names for the matrimony platform.
It avoids manual entry errors, ensures consistency across user profiles, and supports horoscope-based filtering and matching.
π Table Structure
Field Name Data Type Key Description
id INT PK Unique identifier for each raasi
raasi_name VARCHAR β Name of the zodiac sign
is_active BOOLEAN β Indicates whether the raasi is active
β
Validations
id
* Auto-increment
* Primary key
* Not editable from UI
raasi_name
* Mandatory (NOT NULL)
* Minimum 2 characters
* Maximum 100 characters
* Must be unique (case-insensitive)
* Alphabetic characters only
* No leading or trailing spaces
* Duplicate values not allowed
is_active
* Mandatory
* Default value: true
* Accepts only boolean values (true / false)
* Cannot be NULL
* Only active raasi values should appear in user dropdowns
* Inactive raasi should:
*Not be selectable for new users
*Still appear for existing user profiles
* Raasi records must not be deleted once linked to any user