Given the following view that has been created, how would you query the view to list the artist names in ascending order and album titles in desc order? CREATE VIEW album_artist_names AS SELECT album.title, artist.name FROM album INNER JOIN artist ON album.artist_id = artist.artist_id; SELECT * FROM album_artist_names ORDER BY name DESC, title ASC; SELECT * O FROM album_artist_names ORDER BY name, title DESC; SELECT * FROM album_artist_names ORDER BY name DESC, title;

Given the following view that has been created, how would you query the view to list the artist names in ascending order and album titles in desc order? CREATE VIEW album_artist_names AS SELECT album.title, artist.name FROM album INNER JOIN artist ON album.artist_id = artist.artist_id; SELECT * FROM album_artist_names ORDER BY name DESC, title ASC; SELECT * O FROM album_artist_names ORDER BY name, title DESC; SELECT * FROM album_artist_names ORDER BY name DESC, title;

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

In the BOOK_PRICING database, the Category field should be marked as obsolete. Make sure the column has been marked as unavailable.
Using the Winners table from Figure 12-2, write a parameter query that selects only an actor’s Picture field.
Which type of join is demonasted by the folloing query? Select from make. model where make modelID to mode ID a) Non-Equlion b) Self Join c) Cross Join d) Equijoin
Create a View to show the city name of any location that has a department. Only show the city name once in the results. You must use a non-correlated subquery.Call this view: Department_LocationsInclude a second query to display from the View after it is created. Refer to the attached for the table.
create a view named major_ customer. it comsists of the customer num, name, balance, credit_limit and rep_num and rep_num for every customer whose credit_limit is 10000 or less.
The BLOOD_ADMIN_INFO are ORDER ID and LINE. The MAR_ADMIN_INFO MAR_BLOOD_INFO_LN table has one row per blood unit associated with an order. Its primary key columns table has one row per medication administration. The columns ORDER_MED_ID and form the foreign key to the BLOOD_ADMIN_INFO table. Use the followin*query to answer the question below it- SELECT mar.ORDER_MED_ID, mar.SCHEDULED_TIME, mar.TAKEN TIME, bld.BLOOD_ADMIN_TYPE FROM MAR_ADMIN_INFO as mar INNER JOIN BLOOD_ADMIN_INFO as bld What join condition is appropriate in ? AS [Blood Type] Select on of the following: A. mar.ORDER_MED_ID = bld.ORDER_ID B. mar.MAR_BLOOD_INFO_LN = bld.LINE C. mar.ORDER_MED_ID = bld.ORDER_ID AND mar.MAR_BLOOD_INFO_LN = bld.LINE D. It is not possible to join these tables
Table Employee (eid,ename, manager_id,edptid) Show employee with his/her manager name.
DATABASE
PLZ help with the following using ORACLE command sql Use subqueries CREATE TABLE MEMBERSHIP ( MEM_NUM CHAR(3) CONSTRAINT MEMBER_MEM_NUM_PK PRIMARY KEY, MEM_FNAME VARCHAR(30) NOT NULL, MEM_LNAME VARCHAR(30) NOT NULL, MEM_STREET VARCHAR(15), MEM_CITY VARCHAR(10), MEM_STATE CHAR(2), MEM_ZIP CHAR(5), MEM_BALANCE NUMBER (2)); CREATE TABLE RENTAL ( RENT_NUM CHAR(4) CONSTRAINT RENTAL_RENT_NUM_PK PRIMARY KEY, RENT_DATE DATE, MEM_NUM CHAR(3), CONSTRAINT RENTAL_MEM_NUM_FK FOREIGN KEY (MEM_NUM) REFERENCES MEMBERSHIP); CREATE TABLE PRICE (PRICE_CODE CHAR(1) CONSTRAINT PRICE_PRICE_CODE_PK PRIMARY KEY, PRICE_DESC VARCHAR(20), PRICE_RENTFEE NUMBER (3,1), PRICE_DAILYATFEE NUMBER(3,1)); CREATE TABLE MOVIE (MOVIE_NUM CHAR(4) CONSTRAINT MOVIE_MOVIE_NUM_PK PRIMARY KEY, MOVIE_NAME VARCHAR(30) NOT NULL, MOVIE_YEAR CHAR(4), MOVIE_COST NUMBER(5,2), MOVIE_GENRE VARCHAR(15), PRICE_CODE CHAR(1), CONSTRAINT MOVIE_PRICE_CODE_FK FOREIGN KEY (PRICE_CODE) REFERENCES PRICE); CREATE TABLE VIDEO…
Select the query that properly uses table aliases to show the genres of each track in the Album with the id of 6. SELECT genre.name, track.nameFROM trackJOIN genreUSING (genre_id)WHERE track.album_id=6; SELECT g(name), t(name)FROM track AS tJOIN genre AS gUSING (genre_id)WHERE t(album_id)=6; SELECT g.name, t.nameFROM t AS trackJOIN g AS genreUSING (genre_id)WHERE t.album_id=6; SELECT g.name, t.nameFROM track AS tJOIN genre AS gUSING (genre_id)WHERE t.album_id=6;
For this problem create a (temporary) table called instructor_course_nums. Write a procedure that accepts an instructor ID as input. The procedure calculates the total number of course sections taught by that instructor, and adds a tuple to the temporary table consisting of the instructors ID number, name, and total courses taught - call these attributes: ID, name, and tot_courses. If the instructor already has an entry in the table,then the procedure makes sure the total number of courses taught in the temporary table is up-to-date. You must name your procedure: Written in PostgreSQL
JOIN TABLES One row in the PAT_ENC table represents one patient encounter. One row in the ORDER MED table represents one medication order. One patient encounter can have many medication orders but one medication order can only have one patient encounter. In other words, the cardinality of this PAT_ENC to ORDER_MED relationship is one-to- many. You start a query with PAT_ENC. You then add ORDER_MED using an inner join. What is true about the granularity of the result set before and after adding the ORDER_MED table? SELECT ONE OF THE FOLLOWING A. The granularity stays at one row per patient encounter. B. The granularity stays at one row per medication order. C. The granularity changes from one row per patient encounter to one row per medication order on an encounter. D. The granularity changes from one row per medication order to one row per patient encounter.