Changes between Version 9 and Version 10 of BadgesOld

Timestamp:

Nov 14, 2013, 7:56:34 AM (10 years ago)

Author:

brevilo

Comment:

--

BadgesOld

@@ -78 +78 @@
 || reassign_dt : timestamp ||
 
+Different levels of a single badge are supported by simply defining multiple badges, bearing the same title. The SQL rule per badge should be defined such that the different levels are distinguished. That is, define lower '''and''' upper bounds when you intend to use different levels for a badge.
+
 We refrained from adding another relation for tags and de-normalised this attribute in favour of performance. We could use MySQL's SET type to support a bitmap of up to 64 pre-defined tags. However, that list would become part of the data model and would hence be very inflexible. Thus we propose to use JSON as textual representation that can be searched using regular LIKE statements and can be modified easily by available JSON support, e.g. in PHP. Upcoming versions of MySQL and MariaDB are going to include JSON support and will allow more optimised processing. XML would be far too heavy-weight for this purpose.
 
-Badge assignments provide the means to expire old ones by filtering on the `create_dt` attribute. Sorting of badge assignments can be done based on the `reassign_dt`, e.g. newest-first.
+Badge assignments provide the means to expire old ones by filtering (or even removal) based on the `create_dt` attribute. Sorting of badge assignments can be done based on the `reassign_dt`, e.g. newest-first.
 
 === Badge assignment process ===