It's UWAweek 42 (2nd semester, week 12)

help1402

This forum is provided to promote discussion amongst students enrolled in CITS1402 Relational Database Management Systems.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying selected article
Showing 1 of 612 articles.
Currently 121 other people reading this forum.


 UWA week 40 (2nd semester, week 10) ↓
SVG not supported

Login to reply

👍?
helpful
11:46am Thu 3rd Oct, Adam W.

Drops, Creates, Inserts, and a few Selects primarily, I believe the wording suggested that you can include triggers and views, but it wasn't compulsory. I would have to check with Mehwish, but if you have your own test data, that may be sufficient, as long as its enough to show what you need to show. ANONYMOUS wrote:
> Hi, > > I’m a bit confused about what exactly we need to submit in the .txt file. I understand we have to include the DROP statements and the CREATE TABLE statements, but do we also need to submit the sample data, simple queries, and complex queries? > > Additionally, I’m unsure where the assumption files should be placed. > > As mentioned here: "You also need to populate your database (INSERT INTO ...) with some sample data and perform some simple queries to ensure it works correctly. While doing so, I encourage you to try simple and complex queries and also practice the use of Views and Triggers." > > Does this mean we need to submit everything, including views and triggers? > > Lastly, if students are called in for a demonstration, will the database be tested against a standard set of data, or will we be using the data we populated ourselves? I’m concerned that there may be different interpretations of the project requirements. > > Thanks you so much for the assistance.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy