Thu Feb 28

in class

The php scripts that we wrote in class are

• display.php | source
• handler.php | source

Walk through creating a back-end php comment poster.

First, consider a python command-line "summarize-file-and-update" programw which works like this :

$ python comments.py
1. First comment.
2. Second comment.
What is your next comment? This is another

$ python comments.py
1. First comment.
2. Second comment.
3. This is another.

The comments are stored in a file named "comments.txt", in any format you like. Can we do this? Good, let's.

Second, a php web page comment thing ... using exactly the same idea: read the file, loop over the comments, output a div tag for each, put up a form asking for another comment ... when you get one, write it to the file.

resources

• MDN: your first html form
• our php notes

take two : include user login

• python program?
• what do we put in the file(s)?
• several php files ... put form & "action" handler into different files
• form field validation ... client side ?
• storing passwords ?

take three : with a database (i.e. sqlite)

• sqlite.org | wikipedia
• relational database

The big ideas :

• Don't repeat yourself : keep the data in one place, not many.
• database is made of tables for each type of "thing"
• each table is an excel-like spreadsheet grid of rows, each row is one "thing"
• each row has fixed column labels ... and a unique "ID" for each thing
• to refer to one type of thing in another table, use its ID
• relationships between table thing types are one-to-one, many-to-one, or many-to-many
• .... do an example : courses and students . How to store them in a database?

Your mission : put users and comments into a sqlite database, using php ....

Things to think about

• "sessions" ... keeping track of who is logged in with cookies

attachments

		last modified	size
	display_php.txt	Sat Dec 21 2024 04:36 pm	474B
	handler_php.txt	Sat Dec 21 2024 04:36 pm	556B