CS415

Assignments

Watch for updates! This file was last updated on April 18, 2003.

The following dates are tentative and will change during the semester.
Grades Distribution

Assignment Out Due % grade

0 Placement assignment 1/15 1/22 0

1 PostgreSQL Buffer Manager 1/27 2/7 10%

2 PostgreSQL Query Processing 2/10 3/3 15%

3 SQL 3/3 3/12 5%

4 Optimizer assignment and answer template (doc, pdf) 3/13 3/21 5%

5 Application Development 3/28 4/16 10%

6 Normalization 4/18 4/25 5%

	Assignment	Out	Due	% grade
0	Placement assignment	1/15	1/22	0
1	PostgreSQL Buffer Manager	1/27	2/7	10%
2	PostgreSQL Query Processing	2/10	3/3	15%
3	SQL	3/3	3/12	5%
4	Optimizer assignment and answer template (doc, pdf)	3/13	3/21	5%
5	Application Development	3/28	4/16	10%
6	Normalization	4/18	4/25	5%

Frequently updated---check often!!!

Postgres documentation (and getting started guide)
- PostgreSQL: Introduction and Concepts by Bruce Momjian
- Documents on the Home Page of Bruce Momjian
Postgres developer website
- High-level tour
- Internals with pictures
PHP manual
JDBC documentation
DDD: Data Display Debugger
Further reading on hybrid hashing and query execution algorithms:
- Goetz Graefe, Query evaluation techniques for large databases, ACM Surveys, 25(2):73-170.
  Primary reference, section 2.2 in particular (p90 for hybrid hashing and partitioning).
- Kjell Bratbergsengen, Hashing methods and relational algebra operators, Proc. VLDB 1984, pp 323-333.
- Joseph M. Hellerstein and Jeffrey F. Naughton, Query execution techniques for caching expensive methods, Proc. SIGMOD 1996, pp 423-464.

Questions and requests

All questions and requests should go to the TAs.
All regrading requests should be submitted in writing to the TAs, at most 48 hours after the grades are announced. Each written request should include sufficient reason for regrading, in order to br considered.
If your request to regrade a part of an assignment is accepted, your entire assignment is subject to regrading - this means that your grade can go up or down.

Teams

For the non-programming assignments, students are expected to work on their own.
For the programming assignments (i.e., projects 1 and 2) there will be teams of 3 students. Teams of two students are not recommended but are also acceptable -- it is the responsibility of the team to complete the project deliverables, and the grading policy will be the same regardless of the number of members in the team (2 or 3).
When submitting a programming assignment, you should include a GROUPS textfile with the Andrew IDs of the group members.
Only one of you should submit a solution. If multiple solutions are submitted, the latest solution will be graded - NO exceptions!
You are responsible for your teammates and you should solve all team problems on your own.

Late policy

The homework due date and time is the one posted on the web.
To accomodate for coinciding deadlines you may have from other courses, or personal unforseen events such as sickness, each student is granted an automatic extension of 4 calendar days. You can use the extension on any assignment(s) remaining during the semester. For instance, you can hand in one assignment 4 days late, or each of four assignments 1 day late. Slip time can only be used starting Homework 1.
Late days count in increments that are rounded up to the nearest integer. For example, a submission that is 4 hours late will count as one day late.
For group project assignments, the slip time will be deducted from each team member's remaining slip time. This means that in order to use a slip day, all team members must have at least one slip day unused.
When you hand in a late assignment, you must identify at the top of the assignment, (i) how late this assignment is, and (ii) how much of the total slip time you have left.
No assignment will be accepted more then 4 days late or if you have spent your 4-day allowance.
After you have used up your slip time, any assignment handed in late will be marked off 25% per day. No additional extensions will be granted.