llama

It would be \"nice\" now to see this forum phased out and replaced by the new one over at mysqlfreaks.com. I know it must be gradual but the quicker everyone knows where it is the better! We don\'t want to lose this though as it\'s a wealth of info! Could be useful if it\'s properly archived though Maybe if you have someone with a year or so free you could properly index it

I can see the logic behind this set up. But alternatively couldn\'t you have a table for each of the 3 areas (grade/teacher/etc?) and then each row be a different user? The only time this isn\'t suitable is if each username can have many grades/teachers/etc attached to it. When designing a database you want to be looking to normalise the data to prevent redundancy (I\'m sure there is a nice example of this but I don\'t have the url handy maybe someone can help?) It\'s difficult to help without a further understanding of the context.

The only warning I think I should point out is ensure that you validate the data being entered by a user. You can insert some nasty scripts into a hyperlink tag.

I found the most useful method when learning php was to try everything as far as possible using flatfiles for counters/news etc. You will find you get to a stage where you think \"There HAS to be an easier way to keep all this organised and add more so\". This is where mysql comes in and it. Talking from experience now I could never go back to flatfiles but then again that\'s just my humble opinion

I\'m pretty sure that the maximum number of columns is only a theoretical value as other software will have a lower max file size they can handle. http://www.mysql.com/doc/en/Table_size.html Has some good information.

The latest By default its taking the 1st one it encounters, usually the earliest.

I\'m look for any sort of advice as I don\'t really know how to attack this. My basic problem is that I need to SELECT from my table but have it GROUP BY it\'s \"ID\" (many records can have the same id) I then need to display these in date order. When I group by it takes the date as being the date of the 1st record it encounters (this is normally the oldest date for that \"ID\"). So when I then ORDER BY all it does is gives me the order the 1st records with a particular id were created on, obviously not what I want. I\'m thinking to do something such as: SELECT ........... ORDER BY date but then I would need to run another query on the results of the 1st query: SELECT .......... GROUP BY id Any ideas would be appreciated and I\'ll try them out.