my_sql_fetch_array problem

Anon

I am having a problem when I call result3 which gives me the following table

Title Project

everyday 13

Hey!! Guess What? 1

dead ant 8

the end 10

Electronics Project 24

It will not pull up the first row everyday and 13.
help as always is appreciated.

$result3 = mysql_query("SELECT title,project FROM portfolios where ID = $student",$db);

while($myrow=mysql_fetch_array($result3))

{
echo ($myrow["project"]);
echo "<a href=http://10.10.77.10/projects.php?student=" . $student . "&project=" . $myrow["title"] . ">" . $myrow["project"] . "</a><br>";

}

jcarver

That's a tough one, I don't see any immediate answers to that one.

These are some random things that have a small chance of working:
1.Check that Everyday has an ID = $student that is being restricted in the where clause. In fact, if ID is your primary, why is it returning any more than one row?
2.I always include the field that I am testing in the WHERE clause in the fields I am SELECTing. I thought this was a rule, but apparently it's just preference, since you are getting rows at all. Try that and see what happens...

Sorry I couldn't be of much help, because those suggestions are really shots in the dark. But every once in a while those work.

Jason

Anon

This is a project to show off student portfolios, I have arranged the database so that when they upload the picture and the description and the title, that their ID "12345" it put into the ID field, thus I am having multiple entry's of ID 12345, is there a better way of doing this?

jcarver

Hi Damian,

Yes, there is a better way of doing this. It is a database relationship of one-to-many (one student has many files, and one file is owned by exactly one student). This would look like:

(File_ID is an auto-increment unique primary key)
File_ID | Student_ID | OTHER INFO
0000001 00000001 title and description stuff
0000002 00000001
0000003 00000002
0000004 00000001
0000005 00000002
0000006 00000003

This way you have your primary key index uniquely identifying, while still being able to limit the Student_ID in searches for specific students.

I have no idea if this is related to the problem you are having, but it can never hurt to practice good database design.

Good luck,
Jason