CSCE 315 Read-Only Bulletin Board

Last modified: 8/25/13, 11:50PM (Sun)

Newest transactions will be posted on the top. Regularly view this page to see what's going on between other students and the instructor.

All sensitive material such as your name, email address, etc. will be removed, and also any part of code that is not relevant to the discussion will not be uploaded here.


Article List

Date: 10/02 Title: Teams for project 2
Date: 09/06 Title: DB engine required function
Date: 09/06 Title: Team dynamics
Date: 08/25 Title: SVN tips
Date: 08/25 Title: Neat Compiler Trick


Articles

Date: 10/02 Title: Teams for project 2


Report to the instructor if:
* you have any issue with the team assignment.
* your name is missing.
* you requested a reassignment and have not been reassigned.

[501] 

a	Justin Montalvo
a	Shenren Tian
a	Eduardo Cirilo
a	Jacquelynn Liedtke

b	Jonathan Sandell
b	Matthew Carrasco
b	Paul Gaughan
b	Michael Curry

c	Andrew Campbell
c	Trevor Gray
c	James Bowman

d	Vishal Anand
d	Ross Dixon
d	Peter Mack Grubb

e	Edgardo Angel
e	Michael Hudgins
e	Lance Elliot

f	Juan Reyes
f	Kevin Vece
f	Christopher Murray

g	Victoria McCloud
g	Abram Gutierrez
g	Matthew Snyder
g	Ben Sitz

h	Bader Ali-Saleh
h	Nicholas Giunta
h	Jake McKnight
h	Isaac Grande

i	Matthew Horton
i	Harry Zhang
i	Katrina Tuazon
i	Jacob McIntosh

[502] 

a	Faruqui Muhammad
a	Yaofei Li
a	Jose Manriquez
a	Patrick Ruck

b	Saurabh Mishra
b	Abbott, Bradley Michael
b	Michael Karnes

c	Daniel Lake
c	Brendon Hoyt
c	Eric Heisler

d	Ricardo Zavala
d	Austin Dalton
d	Menard, Andrew Myers
d	Caleb Bogenschutz

e	Colt Campbell
e	Cory Maughmer
e	Chuong Trinh

f	Huy Nguyen
f	Burgess, Juaune
f	Josh Latvatalo

g	Hao Sun
g	Thomas Creighton
g	Nathaniel Adkins

i	Joshua Amaku
i	Josh Kruger
i	Harrison Kurtz
	
[503] 

a	Shane Buckner
a	Travis Olbrich
a	John Leslie
a	Derek Burgman

b	Husain Alshehhi
b	Ramon Orduno
b	Shihua Zheng
b	Valente Ubaldo

c	Johnny Lagunas
c	Thomas Mulholland
c	Pranav Rao
c	Zachary Dunn

e	Josh Privett
e	Brooke Griffith
e	Adam Pitones
e	Derek Shepherd

f	Patricia Mullgrav
f	Devan Huapaya
f	Mellisa McNiell
f	Karan Khatter

g	Wesley Tang
g	Grace Coffman
g	Sidian Wu
g	Alejandro Vega
g	Violeta Torres

h	Kuo-Wei Chiao
h	Richard Wilder
h	Eduardo Cestafe
h	Alex Oborny
Date: 09/06 Title: DB engine required function
Hi everyone,

For Monday's submission (9/9/2013), you need to include the following DBMS functions:

create table
insert into
delete
selection
projection
renaming
set union
set difference
cross product
update
show

You don't need to implement the following:

open
close
write
exit

[added 9/9/2013]
For the selection function, for now, focus on implementing

        attr == value

if you are having difficulty implementing an arbitrary logical
expression as the condition.

Implementing the full condition can be done later once the
parser is done (parser + DBMS submission).



Date: 09/06 Title: Team dynamics
Hi everyone,

I'm hearing from some students that certain teams are not functioning
properly. The main issue seems to be the lack of communication.

Each team should have a fixed time to meet outside of the lab and the
lecture. For example, MWF 6-7pm, TR 7-8pm, etc. Exact time and day do not
matter.

Also, everyone is expected to respond in a timely manner to other team
members' emails, text, etc.

Finally, if you are in a team with unresponsive members, do the work on
your own, to the best of your ability. You should not sit and wait not
doing anything while waiting for your team mate's response. For example,
for the DB engine, write code for create, insert, show, and make sure they
work properly. If you have time, get projection to work, etc. The key here
is to implement a small functioning subset so that you can get partial
credit. It does not help to write incomplete code for all required
operators, since you won't get much partial credit that way.

Functioning members in a dysfunctional team will get their project score
multiplied by 1.x to compensate for their disadvantage. Dysfunctional
members will be penalized by multiplying their final project score with
0.x.

Date: 08/25 Title: SVN tips

----------------------------------------
I. Here's how you set up SVN through a ssh tunnel:
----------------------------------------

1. Run putty on your local machine

        - set the host to sun.cs.tamu.edu
        - select SSH protocol
        - go to the ssh tunneling menu
                - source port: 5555
                - destination: svn.cse.tamu.edu:443
                - click [Add]
        - save the session
        - connect

2. Verify connection with your browser (on your local machine):

        - go to the following in the browser:

	https://localhost:5555/CSCE315_501_502_503_SVN_ASSIGNMENT1DB_TEAM0X

        - enter username/password.

        - you'll be able to see your directory.

----------------------------------------
II. Browsing the SVN repository
----------------------------------------

Once you set up ssh tunneling as described above,

1. open Tortoise SVN setup (right click on any file)

2. select the repository browser
 
3. enter

        https://localhost:5555/CSCE315_501_502_503_SVN_ASSIGNMENT1DB_TEAM0X

   in the URL box

4. when a warning box pops up, accept it.

5. enter username and password in pop-up box.

6. the rest is the same (see below).

----------------------------------------
III. Basic SVN repository setup
----------------------------------------

1. Open the repository browser and connect to your server.

2. Import: Drag your source code folder from your desktop into the repository 
   browser so that you can have the folder under SVN control.

3. CheckOut: To make your local copy under SVN control, you must first 
   check out the folder from the repository browser. (First rename your
   existing folder and acrhive it somewhere else.) Look for this menu
   in the Repo browser.

4. Update: Before you edit your local copy, pull any changes that may have
   occurred. You can access this function by right-clicking on the local copy
   of your folder or individual files.

5. Commit: Once you're done with modifying your local copy you can now send it
   to the SVN repository.

Date: 08/25 Title: Neat Compiler Trick

Here's a small trick to make it easier to define tokens and their corresponding
strings. See Steve Oualline, Practical C++ Programming, O'Reilly and Associates, Inc., 1995. pp460-461.

//----------------------------------------------------------------------------
//  Using the define trick to generate tokens and their strings
//----------------------------------------------------------------------------

#define _TOK T(_tik),T(_tak),T(_tok),T(_toe)

#define T(X) X
enum TOKTYPE { _TOK };

#undef T
#define T(X) #X
char TOKSTR[4][20]={ _TOK };


// The above is equivalent to

enum TOKTYPE { _tik, _tak, _tok, _toe };

char TOKSTR[4][20]={"_tik", "_tak", "_tok", "_toe" };


$Id: board.php,v 1.5 2004/08/30 23:54:24 choe Exp $