Parameterization and databases

During the next couple of days, all of the SQL will be parameterized using mysqli. This will make the database much more secure(protecting from SQL injection) as well as make the code more readable and editable.

We are also looking into alternatives for compatibility that require less updates and/or less databases. Our first idea was a user by user table, so 1 possibly 1000000by1000000 table. But Eric mentioned that adding columns can be very time consuming. The obvious alternative is a table with 3 columns, userA, userB and score. This would be a 1000000*1000000by3 table, which requires no column adds, but the 1000001st user will require 1000000 new rows to be added. The last idea we thought of was having a separate table for each user. So 1000000 1000000by2 tables. Not sure right now which one we are going to go with, or if there is a better option.

RCOS meeting

After our second presentation we were given a good idea regarding database efficiency. Now the compatibility table doesn't exist as one table, which requires a column add, which is as we found out very expensive. It is now a series of tables for each user. This allows for row adds instead of column adds, and makes searching for top compatible people very easy.

The issue of security was also brought up, and we are looking for good ways to protect from SQL injection/html injection in php/javascript.

Databases again

Recently I learned in my databases class the greatness of foreign keys with on delete cascade. So I decided to implement that in the system to make deletion of shows and people easier. While changing the structure, I had to remake all the databases, which allowed me to make new entries, and check a lot of my functionality that was made recently. Through that process I found a few bugs, and fixed them.

Profile Page in Place for now

Right now we're just getting basic structures in place so we can link around to them. After taking this step we can add more functionality to each section in bits and pieces, but first we want to make sure we have some ground work.

On that note the base profile page is done, and a show page framework will be up next. We realize that we wanted to work on an idea of this site being customizable for everything, but we think this will be easiest expanding from a concrete idea just so we can get something out the door to further develop.

Compatibility

The compatibility algorithm has been implemented at a core level. There will be more optimizations added later, as well as a part to the profile page which displays the top 5 compatible people.

Databases

Now that a lot of the base databases have been set up, as well as basic UI for them, the next step is the long awaited implementation of the compatibility database.

Progress

The project is progressing well, there is a home page, and a table page. There is registration, login/logout capability which also means the users database has been created. Some style oriented changes are starting to be added. We hope to get a show page, as well as search functionality and user profile pages in the near future.

DB Design Proceeds

We're coming right along with designing our database before we get really going. We think we've got a basic layout of what every site might ask to be stored. It's also given us a chance to review and create the compatibility algorithms we're going to implemented. Stay tuned for the beginning of the code updates.

First post

This is the first post, with a possible logo(55X55 pixels):

A big thanks to Mr. Sean O' Sullivan for funding this open source project.