Note: all custom commands are prefixed by "jdb-". * Command-line interface and Custom commands to be Implemented* Appropriate error messages must be shown when invalid commands are given, or nonexistent tables or columns are referenced.Įxample command-line interaction scenario is shown below.In addition to the above, at least 5 custom commands must be designed and implemented that may be used toward phase 3 and phase 4.Both axes should be scaled automatically to fit the histogram data. The x axis is frequency, and y-axis is the bins. jdb-stat (or ) Given a (or a ), return basic statistics such as min, max, mean, median, and print out a histogram (using ASCII characters).jdb-search-and-join Given and that are connected through multiple other tables, produce a joined table where rows in table1 with multi-hop linkage to the entries in table 2 appear on the same row in the resulting joined table.jdb-search-path Given two table names and, find the path of intermediate tables you have to go through from to reach.jdb-find-column Find all tables that have.Print the list of (table_name, column_name). jdb-show-all-primary-keys Show all primary keys from all tables.List all other tables that have in their column one or more of the primary keys of the table. jdb-show-related-tables Given the table ,.(Note: This seems too many, but these mostly correspond to finding the right SQL query and passing on to the server.) In addition, implement the custom commands shown below.(Just pass on the string to the server and display the returned results.) All SQL commands should be be accepted as is (in READ-only mode - no creation of tables, inserts, etc.).For this, you will need to write a basic command line interpreter (this will have a really simplt syntax, so you can just use as switch statement). The main user interface is a simple command line interface, taking user input from keyboard and printing out the results on the screen.
Connect to MySQL server, with proper authentication credentials, and disconnect properly.The specifics may vary depending on your design from phase 1, but the Java application should demonstrate the following functions and requirements. JDBC Basics, by Oracle is a good place to start.įor this phase, your team will develop basic function in a Java application to serve as the DB client.
#Assignments on adventureworks database update#
JDBC allows you to connect to a DB server (e.g., a MySQL server or Postgres server, etc.) and send queries, get the results back, and update the entries.
Select * from information_lumns where column_name like '%productphotoid%' Select count(orderdate) from salesorderheader group by orderdate order by orderdate Select e.employeeid, e.addressid from employeeaddress e inner join address a using(addressid) Select * from customer where AccountNumber="AW00029475"
Key functionality your DB client will provide.While doing this, think about what kind of queries may be helpful to a user.īased on this initial hands-on investigation of the data, you will produce the following: What are the columns, what are the keys, etc., and how they are all connected. Once you're ready, you should explore the database: what tables it has, Is mostly about the design document, you must play with the actual MySQL server with the AdventureWorks DB loaded in order to write the specification. First, set up your MySQL server environment and load up the AdventureWorksĭatabase to the server (see the README file in 315-db repo).
0 kommentar(er)
