You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A full-featured hospital operations application built with Oracle APEX 26.1,
repo/
├── ALNOOR_SCHEMA.sql # All 13 table definitions — run this first
├── ALNOOR_Full_Data_Load.sql # Sample data: 20+ patients, 10+ doctors, 5+ departments,
│ # 20+ medicines, 30+ appointments, 10+ visits & prescriptions
└── f103.sql # Full Oracle APEX application export (App ID 103, APEX 26.1)
Run the scripts in this exact order using a SQL client (SQL Developer, SQL*Plus, or the APEX SQL Workshop) connected as the schema owner.
Step 1 — Create the schema objects
@ALNOOR_SCHEMA.sql
Step 2 — Load the sample data
@ALNOOR_Full_Data_Load.sql
Step 3 — Import the APEX application
In Oracle APEX:
Go to App Builder → Import
Upload f103.sql
Set the parsing schema to ALNOUR-DB
Click Install Application
The application will be available immediately after import. Log in and navigate to the Home Dashboard to verify the KPI cards populate correctly.
thanks.
Title Format: The title should start with a ClickUp ticket ID (e.g. "86ex6r17g: ") instead of “[Oracle apex]” to adhere to the naming convention.
Description Accuracy: The pull request description should reflect changes made in the pull request, detailing any specific features or bug fixes introduced, and not just the basic functionality.
Indentation Consistency: Ensure all indentation is consistent with the standard of 4 spaces throughout all SQL files.
Blank Lines: Check for and remove any unnecessary blank lines throughout the code files to improve clarity and readability.
Logic Errors: Review the entire SQL code for logical errors or areas that could benefit from optimization or improvement.
Script Execution Order: In the documentation, emphasize the expected order of script execution more clearly.
File Comments: Add explanatory comments in each file detailing script purposes, potential side effects, or dependencies on other scripts.
This concise set of comments addresses the necessary adjustments while maintaining relevance to specific lines or sections in the pull request.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A full-featured hospital operations application built with Oracle APEX 26.1,
repo/
├── ALNOOR_SCHEMA.sql # All 13 table definitions — run this first
├── ALNOOR_Full_Data_Load.sql # Sample data: 20+ patients, 10+ doctors, 5+ departments,
│ # 20+ medicines, 30+ appointments, 10+ visits & prescriptions
└── f103.sql # Full Oracle APEX application export (App ID 103, APEX 26.1)
Run the scripts in this exact order using a SQL client (SQL Developer, SQL*Plus, or the APEX SQL Workshop) connected as the schema owner.
Step 1 — Create the schema objects
@ALNOOR_SCHEMA.sql
Step 2 — Load the sample data
@ALNOOR_Full_Data_Load.sql
Step 3 — Import the APEX application
In Oracle APEX:
Go to App Builder → Import
Upload f103.sql
Set the parsing schema to ALNOUR-DB
Click Install Application
The application will be available immediately after import. Log in and navigate to the Home Dashboard to verify the KPI cards populate correctly.
thanks.