8 Commits

Author	SHA1	Message	Date
Dan Johnson	2e478d8537	TopicLinkClick: convert 'ip' (bigint) -> 'ip_address' (inet) ... When accessed over IPv6, the ip address of the user is a 128-bit number, too big for PostgreSQL's bigint data type. Since PostgresSQL has the built-in inet type, which handles both IPv4 and IPv6 addresses, we should use that instead. Where this is done elsewhere in the codebase, the column is called ip_address, so we should follow that convention as well. This migration uses a SQL command to populate the new field from the old one, so as not to rely on the TopicLinkClick model class, which should keep the migration from failing if that class is modified in the future.	2013-06-25 19:41:19 -04:00
Sam	870e59883b	secure the links on the topic pages, eliminated deleted topics as well.	2013-06-05 16:10:26 +10:00
Sam	74502172f3	speed up test	2013-06-05 12:48:34 +10:00
Gosha Arinich	cafc75b238	remove trailing whitespaces ❤️	2013-02-26 07:31:35 +03:00
Robin Ward	dee9e9a51f	Fix bug where links to posts weren't being tracked	2013-02-13 15:23:09 -05:00
Robin Ward	09e53c72d4	Changed our minds: Let's track internal links, just never to users. Something like FAQ is useful.	2013-02-11 12:36:33 -05:00
Robin Ward	f21609fe2e	Don't track links within discourse unless they're to other topics.	2013-02-11 11:11:48 -05:00
Robin Ward	21b5628528	Initial release of Discourse	2013-02-05 14:16:51 -05:00