You need to work with your group members. You are required to Create a Database following a Gym membership, Insurance Company, Bank or School using your own Student ID as the Collection Name. You need to populate your documents using 7 different data and follow with 3 Update and 2 Delete, 1 Drop Collection and 3 Find Commands in your Codes. All the steps you make has to be documented using PDF file, and make sure you take the screenshot of the Mongo and the Node command prompt.

You need to work with your group members. You are required to Create a Database following a Gym membership, Insurance Company, Bank or School using your own Student ID as the Collection Name. You need to populate your documents using 7 different data and follow with 3 Update and 2 Delete, 1 Drop Collection and 3 Find Commands in your Codes. All the steps you make has to be documented using PDF file, and make sure you take the screenshot of the Mongo and the Node command prompt.

Oracle 12c: SQL

3rd Edition

ISBN:9781305251038

Author:Joan Casteel

Publisher:Joan Casteel

Chapter5: Data Manipulation And Transaction Control

Section: Chapter Questions

Problem 3HOA: Save the changes permanently to the database.

See similar textbooks

Similar questions

Save the changes permanently to the database.
Create a new database using phpmyadmin (or any other method you choose). The database should have at least two tables: One table should be able to store the username and password of users for session management. Insert one record in this table for use later in the project. The second table should be able to store the articles written by the user. The only information we need for articles is the author (which would be a user of the system), the title of the article and the content of the article. The content field should be able to store at least a thousand characters. Insert one simple record in this table for use later in the project H4
The Developers team also wants you to ensure that emails are converted to lowercase after an update operation. Currently, new insertions are guaranteed to have lowercase emails, but there is no such guarantee for legacy emails. Therefore, the team wants to ensure that emails are being retained in a lowercase irrespective of any changes in the database. Create a new TRIGGER called email_update for the USERS table that runs before an UPDATE operation. Task Create a TRIGGER to run on the USERS table before any UPDATE operation.
Devise a datasheet in access based on a subject table that allows a user to enter information about a subject. Your subject table should have at least ten (10) fields, including:- A primary key field to identify the record ([aut*-RecordIdentifier]).- A single field alternate key.- AT least one date field.- At least one number field.- The standard fields.- Any other fields that you think are appropriate.
Use the iloc() function to extract the first 20 features of the dataframe har_train. Save this new dataframe to first_twenty. Next, using the seaborn library create a heatmap for the correlation matrix. First you have to create the correlation matrix from the pandas dataframe (save it in a dataframe called corr) and then plot it using seaborn with these customizations: Set the seaborn style to white. Generate a mask using np.triu(np.ones_like()) with the dtype as boolean to only show the lower triangle of the correlation matrix. Save it in a variable called mask. Set up the figure with matplotlib with figsize=(11,9). Use fig, ax = ... Generate a custom diverging colormap for the heatmap with the arguments (220, 10, as_cmap=True). Save it in a variable called cmap. Draw the heatmap with the mask and correct aspect ratio, using the arguments corr, mask=mask, cmap=cmap, vmax=.3, center=0, square=True, linewidths=.5, cbar_kws={"shrink": .5}). Finally, use fig.tight_layout() just before…
Using the undo tablespace rather than the backup segment is recommended due to its many advantages. Do you have any evidence to support your claims?
There are several reasons why the undo tablespace should be used instead of the backup segment. Do you have proof to back up what you're saying?
Task 5: The Developers team also wants you to ensure that emails are converted to lowercase after an update operation. Currently, new insertions are guaranteed to have lowercase emails, but there is no such guarantee for legacy emails. Therefore, the team wants to ensure that emails are being retained in a lowercase irrespective of any changes in the database. Create a new TRIGGER called email_update for the USERS table that runs before an UPDATE operation.
Add a calculated field named AccountTime that calculates the number of days each client’s accounts have been open. Assume today’s date is 12/31/2017. Recall dates must be enclosed in # to denote to Access it is a date. How would I put this in access?
Create a set of lookup tables.
Create a MySQL Database called “CSC306Class”. Create three (3) tables in the database called “studentInf”, “IntructorInf”, and “LikedAndDisliked”. Each table should consist of five columns that are relatable to the table name. Insert at least five row of data in each table. The data can be any information as long as it is related to the table name.
The InstantRide User Satisfaction team are looking forward to creating discounts for the users. However, the team suspects that there could be duplicate users in the system with different emails. Check for the users with their names and surnames for potential duplicates. Therefore, you need to JOIN the USERS table with USERS table and compare for equality of USER_FIRST_NAME and USER_LAST_NAME and difference in USER_ID fields. Output supposed to look exactly like so : USER_ID USER_FIRST_NAME USER_LAST_NAME USER_EMAIL USER_ID USER_FIRST_NAME USER_LAST_NAME USER_EMAIL 3008 Nursin Yilmaz n.yilmaz@xmail.com 3003 Nursin Yilmaz n.atak@gmail.com 3003 Nursin Yilmaz n.atak@gmail.com 3008 Nursin Yilmaz n.yilmaz@xmail.com