StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11065270
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
18
CommunityOwnedDate
CreationDate
2012-06-16T16:43:21.147
FavoriteCount
0
LastActivityDate
2012-06-26T13:47:55.980
LastEditDate
2012-06-26T13:47:55.980
LastEditorUserId
1100552
OwnerUserId
1100552
ParentId
11065212
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
First of all: This is not the way I would write a click counter. That said, 100 users hitting your server at the same time (with initial clicks at 0) might result in a recorded number of 1..100 with low (=wrong) values being prominent. <ul> <li>If you want to count in a text file, lock as in @lanzz's answer and be prepared for a major performance hit - you are effectivly serializing the requests.</li> <li>If you want to count in any file, consider SQlite and prepare for a manageable performance hit</li> <li>If you just want to count, consider a real DB with a very small performance hit</li> </ul> EDIT: Implementations I created the below implementations for a file counter in a text file, SQLite and MySQL Please do not flame me for using the <code>mysql_*()</code> function family - as allways the code is meant to be instructive, not productive: instructive in the sense of concentrating on the issue at hand, not the surrounding layers. counter-file.php: <pre><code><?php //acquire file handle $fd=fopen('counter.txt','c+b'); if (!$fd) die("Can't acquire file handle"); //lock the file - we must do this BEFORE reading, as not to read an outdated value if (!flock($fd,LOCK_EX)) die("Can't lock file"); //read and sanitize the counter value $counter=fgets($fd,10); if ($counter===false) die("Can't read file"); if (!is_numeric($counter)) { flock($fd,LOCK_UN); die("Value in file '$counter' is not numeric"); } //increase counter and reconvert to string $counter++; $counter="$counter"; //Write to file if (!rewind($fd)) { flock($fd,LOCK_UN); die("Can't rewind file handle"); } $num=fwrite($fd,$counter); if ($num!=strlen($counter)) { flock($fd,LOCK_UN); die("Error writing file"); } //Unlock the file and close file handle flock($fd,LOCK_UN); fclose($fd); printf ("Counter is now %05d",$counter); ?> </code></pre> counter-sqlite.php: <pre><code><?php //counter.sqlite3 was created with //CREATE TABLE counter (counter NUMERIC) //INSERT INTO counter VALUES (0) //Open database $dsn='sqlite:'.dirname(__FILE__).'/counter.sqlite3'; $db=new PDO($dsn); if (!$db) die("Can't open SQlite database via DBO"); //Make exclusive $sql="BEGIN EXCLUSIVE TRANSACTION"; if ($db->exec($sql)===false) die("Error starting exclusive transaction"); //Update counter $sql="UPDATE counter SET counter=counter+1"; if (!$db->exec($sql)) die("Error inserting into database"); //Read value $sql="SELECT counter FROM counter"; $result=$db->query($sql); if (!$result) die("Error querying database"); foreach ($result as $row) $counter=$row['counter']; //Commit $sql="COMMIT TRANSACTION"; if (!$db->exec($sql)) die("Error committing to database"); //Print result printf("Counter is now %05d",$counter); ?> </code></pre> counter-mysql.php: <pre><code><?php //mysql database was created with //CREATE TABLE counter (counter INT NOT NULL) //INSERT INTO counter VALUES (0) //Open database connection and select database $db=mysql_pconnect('127.0.0.1','redacted','redacted'); if (!$db) die("Can't open database"); if (!mysql_select_db('redacted', $db)) die("Can't select database"); //Update counter $sql="UPDATE counter SET counter=counter+1"; $qry=mysql_query($sql,$db); if (!$qry) die("Error updating database"); //Read value $sql="SELECT counter FROM counter"; $qry=mysql_query($sql,$db); if (!$qry) die("Error reading from database"); $counter=mysql_fetch_array($qry,MYSQL_ASSOC); if (!$counter) die("Error reading result"); //Print result printf("Counter is now %05d",$counter['counter']); ?> </code></pre> As for the performance: I stand corrected. The SQLite implementation is 100 times slower than the two others - this is because I had to accept, that nothing else than <code>START EXCLUSIVE TRANSACTION</code> would end a test of <code>ab -n 1000 -c 50 http://127.0.0.1/stackoverflow/counter/counter-sqlite.php</code> with 1000 clicks counted. My recommendation for the OP is to use the MySQL version - it is fast and will reliably save the counter over an OS crash. The file version has nearly the same performance characteristics, but it can quite easily be destroyed by an OS crash.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWill the server handle two or more at the same time?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USEugen Rieck
UserOwnerUserId
1. USEugen Rieck
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWill the server handle two or more at the same time?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.