Tournamatch version 3.20 is now available.
- Massive rewrite of the data access layer.
- Removed several legacy and proprietary classes from our source code
Data Access Layer Rewrite
If there was an award for “Least Sexy Update”, this release would be the Tom Brady of Tournamatch updates (Go Bucs!). Kicking off the major highlights for version 3.20 is a complete rewrite of our data access layer. Tournamatch no longer uses the proprietary MySQLi proprietary adapter classes for database access. Every call has been replaced with the native WordPress database access abstraction.
Why is this relevant? For quite a few reasons, actually. Security is the biggest reason. Every applicable query is now sanitized using the methods vetted by the WordPress community. Using the WordPress database access abstraction also causes Tournamatch queries to show up in debugging and performance analysis plugins. It supports more code features which should reduce code in the software (less is more), has caching mechanisms, and this moves us one step further to supporting multisite setups.
Legacy Code Scrub
To piggy back off of the above change, this release removed several legacy proprietary solutions for things like file uploads, script hooks, and data access. As much as we love to write code, writing proprietary code is generally a bad thing. Using native code that has been vetted by the WordPress means Tournamatch is more secure, easier to extend, and easier to develop moving forward.