Download Database Catalogs - File Processing - Programming Assignment IV | CSCI 2230 and more Assignments Digital Signal Processing in PDF only on Docsity! CSCI 2230-201 Programming Assignment #4 Due: 20 April Database Catalogs, Continued Goals This assignment will add searching for records and deleting records to the program from Programming Assignment 3. As before, you must implement your solution on einstein. This program must be done in your previously assigned groups. 1. Startup The program should start up in the same manner as Programming Assignment 3: create a subdirectory if needed, create the new catalogs, then accept and process the same commands as in Programming Assignment 3. 2. New Commands As with previous assignments, read commands from the standard input. Do not prompt for them. a. Find Record. Command: F filename attrname operator attrvalue The value of operator will be one of { =, <, >, # }, where # means "not equal to". Find and display the records in filename whose value on the field attrname is equal to, less than, greater than, or not equal to, the value specified in attrvalue. Look up the filename in the relcat; if not found, report an error. Look up the attribute information of filename in the attrcat. If attrname is not a valid field, report an error. Then search filename sequentially, looking for all matching records. Display any matching records using the same table format as the D (display) command. Note that you must compare fields to values based on the field's type - for example, if the field's type is D (double), use double values to compare them. Example: F employee name # Jones Display all employee records whose name field is not Jones Example: F student gpa > 3.00 Display all student records whose gpa field is greater than 3.00 b. Delete Record. Command: X filename attrname operator attrvalue Similar to part a, but delete any record that matches the criterion. Example: X student name = Miller Delete all student records whose name field is Miller Deliverables Be sure to test your program carefully. Your program should handle most reasonable errors - when in doubt, ask. Submit a printout of your program, a copy of your make file, a UML diagram of classes used and their relationships, a UML sequence diagram for each command, and your test suite in a manila envelope with project coversheet attached to the front. Copy an executable version of your program named hw4 in your home directory. Make sure the permissions are set correctly by doing the command chmod go+rx hw4 after you copy the executable to your home directory. Have your partner check from his account to ensure that he can execute hw3.
