Skip to main content

Timeline for Designing an ad banner tracker

Current License: CC BY-SA 4.0

14 events
when toggle format what by license comment
Dec 8, 2019 at 3:05 review Close votes
Dec 9, 2019 at 20:01
Dec 5, 2019 at 11:51 history edited Ian Y. CC BY-SA 4.0
added 7 characters in body
Dec 5, 2019 at 11:42 history edited Ian Y. CC BY-SA 4.0
added 11 characters in body
Dec 4, 2019 at 8:48 history edited Ian Y. CC BY-SA 4.0
added 126 characters in body
Dec 4, 2019 at 7:42 vote accept Ian Y.
Dec 4, 2019 at 5:18 comment added Rick James Caution when using INSERT IGNORE or IODKU: The next auto_inc value is grabbed before deciding whether to do an INSERT. That is, it will "burn" some ids.
Dec 4, 2019 at 5:15 comment added Ian Y. @RickJames Thanks for pointing out the wrong code. I just updated the CREATE TABLE `Unique Impression IP` and SQL queries. And thank you and @danblack for suggesting using INSERT ... ON DUPLICATE KEY UPDATE ...
Dec 4, 2019 at 5:12 history edited Ian Y. CC BY-SA 4.0
added 79 characters in body
Dec 4, 2019 at 5:04 comment added Rick James The INSERT looks wrong. You check by banner and IP, but then insert only IP. It might be possible to fold those 4 SQLs into a single INSERT ... ON DUPLICATE KEY UPDATE ... That would be faster. In the 'SELECT', why test both ID and IP, when ID is known to be UNIQUE (because it is the PRIMARY KEY)?
Dec 4, 2019 at 3:37 answer added danblack timeline score: 1
Dec 4, 2019 at 3:16 history edited Ian Y. CC BY-SA 4.0
added 1640 characters in body
Dec 3, 2019 at 23:43 comment added danblack insert on duplicate key update maybe the general form of a counting query. IPs aren't people either. Commonly attacked problem that probably has solution existing already. Also look up preventing SQL injection. Once other browser header fields are added you will be vulnerable.
Dec 3, 2019 at 15:20 review Close votes
Dec 3, 2019 at 15:22
Dec 3, 2019 at 14:36 history asked Ian Y. CC BY-SA 4.0