• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

School project - database

Status
Not open for further replies.
I'm studying to be a datatechnician and I'm only 15 months away from graduation. The whole thing takes more than 5 years to complete.

Anyways I'm going through a school session and we have to end it with a project and a test.

This session is all about C++ (Borland Builder) and (Microsoft) SQL. We have two weeks to do the project. The teacher said he would be happy if we used more than one table (relations).

We have to come up with our own program and i have no clue to what I should do. There are many of the typical movie/music/book collection databases and so on. It just seems so boring.

I was thinking about a mini SQL manager. Creating databases, tables, columns, datatypes and giving them values and so on. Now the first problem is the login part which I hope someone can help me out with. My SQL book doesn't say anything about it.
 

Azih

Member
simplest way is to just make a users table with username and password fields. Then on login just check that the password/username pair exists in the table.

Not exactly secure, but good enough, and I think all login schemes follow that pattern just with a whole lot more encryption going on.

Edit: Though I have no idea what you're trying to accomplish. What exactly is the mini SQL manager doing
 

Phoenix

Member
Azih said:
simplest way is to just make a users table with username and password fields. Then on login just check that the password/username pair exists in the table.

Not exactly secure, but good enough, and I think all login schemes follow that pattern just with a whole lot more encryption going on.

Edit: Though I have no idea what you're trying to accomplish. What exactly is the mini SQL manager doing

And actually if you encrypt the passwords in the database and then encrypt the password the user gave you, you can do a:

select * from users where username= $, password = crypt($)

passing in the password. If the password is wrong you won't have any results back.
 
That was fairly easy. The crypt part is a little troublesome.

My manager was supposed to logon to the actual server. Kinda like the real sql managers. I think it's way too much work for two weeks and the program would never use tables just create them.

I'm back to movie/book/game database. I don't know anything about mixing drinks.
 

Tarazet

Member
Yeah, just stick with basic projects. I've never encountered a situation where I was asked to be creative in college. Just go through the motions really well, and save the brilliant ideas for when you can actually make money off of them.
 
Status
Not open for further replies.
Top Bottom