Added by Aye Aye Aung about 1 year ago. Updated 9 months ago.
100%
Description
Implement CRUD operations for pricing packages.
Develop functionality to define and manage key features for each package (e.g., Free, Standard, Premium).
Set and manage pricing for each package, including associated features.
pricing_packages_tbl
id (BIGINT UNSIGNED)
name (VARCHAR(255))
description (TEXT)
price (BIGINT)
created_at (TIMESTAMP)
updated_at (TIMESTAMP)
Here is the sample package.
Package 1: Free
Name: Free
Description: A basic, no-cost package suitable for smaller-scale or trial use.
Price: 0 MMK
Created_at: NOW()
Updated_at: NOW()
Package 2: Standard
Name: Standard
Description: Standard package with medium features. Best for moderate usage.
Price: 1999 MMK
Created_at: NOW()
Updated_at: NOW()
Package 3: Premium
Name: Premium
Description: Premium package with full features. Ideal for large scale use.
Price: 4999 MMK
Created_at: NOW()
Updated_at: NOW()
We need to add following database field and modified CRUD
pricing_packages_tbl
id (BIGINT UNSIGNED)
name (VARCHAR(255))
description (TEXT)
voter_limit (INT) - Max number of voters allowed
features(json) - List of features included in JSON format
price (BIGINT)
is_active(Boolean) - Whether the package is currently offered
created_at (TIMESTAMP)
updated_at (TIMESTAMP)