OpenLampTech issue #126
Threat to open source | DML in SQL | WooCommerce Blocks and Core updates | ROW_NUMBER() in MySQL | CodeIgniter 4.5.0 release
Thank you for reading the OpenLampTech newsletter!
If someone awesome shared this newsletter with you and you are not yet subscribed, please use the Subscribe button below and join:
OpenLampTech has sponsorship opportunities for your brand, product, or service in the weekly newsletter. As an independent publication, collaboration is very affordable.
All commentary and opinions are mine unless otherwise quoted.
Changes to Store API loading for performance
These will be upcoming changes implemented in WooCommerce 8.9 (scheduled for May 2024).
Based on my understanding, in this change, the rest API calls will now only involve the needed controller and not load all of them as in previous versions.
To note this is a backwards incompatible change and it is suggested to verify if you're using any of these filters to modify Store API requests:
rest_request_after_callbacks
rest_dispatch_request
[Woo Developer Blog]
How to Use Data Manipulation Language (DML) in SQL
Without SQL Data Manipulation Language (DML) commands, you wouldn't be able to store, change, or remove the data in a database. While this article covers a different SQL implementations’ syntax, the same 3 key commands are used in MySQL as well:
INSERT
- Create new row(s) of data.UPDATE
- Change or modify existing data.DELETE
- Removes or deletes existing data.
[The New Stack]
WooCommerce 8.8 is Delayed (04-05-2024)
By the time you're reading this, WooCommerce 8.8 should have been released. Even with the pushback date of 04-10-2024 from 04-09-2024.
Curious as to what the delay is for?
Very shocking to me.
Probably for you too.
Read to find out.
Makes me wonder if is WooCommerce losing market share at a greater rate than realized.
[Woo Developer Blog]
Learn the Tricks of Using ROW_NUMBER() in MySQL 8
This article has several different example queries using the ROW_NUMBER()
Window Function. There are some workaround queries written for MySQL v5.7 since ROW_NUMBER()
is natively available in MySQL v8 and up (but not v5.7).
However, MySQL v5.7 has reached EoL so it's not advisable to use that version.
With ROW_NUMBER()
you can determine all sorts of results for top N queries along with other more advanced query techniques.
[Medium]
CodeIgniter 4.5.0 release (April 7th, 2024)
My favorite framework has an update with some enhancements and other additional changes. Be sure and read the changelog to see them all.
Here are a few that grabbed my attention:
Dropped support for PHP 7.4
FileLocator caching
remove deprecated upper functionality in
Request::getMethod()
fix: QueryBuilder
limit(0)
bugfeat:
db:table
shows db config - (Interesting and seems like a useful spark command 🙌)
[CodeIgniter Github]
The threat to open source comes from within
If you read only one article shared in this week's OpenLampTech newsletter, I hope it is this one. While the author states he is not an expert, in my opinion, he definitely has some ‘exceptional expert thoughts’ on a whole lot of scuttlebutt going on in the open-source world.
As a user and champion for open-source myself (hence a lot of open-source-related content shared in OpenLampTech), I'll admit I totally slept through the recent XZ issues in the Linux ecosystem.
WooCommerce Blocks 11.7.0 Release Notes (April 9th, 2024)
Moving forward after this release, WooCommerce Blocks will be a part of the WooCommerce Monorepo.
Here are a few highlights that caught my eye:
woocommerce_single_product_summary
action hook - The content you want to display is now shown above the product summary on the Single Product template.Fix: HTML Entity Decoding in Taxonomy Controls
Validate coupon usage against customer ID and emails
Pass order ID to
woocommerce_before_thankyou
hook - Makes sense to me as is noted that this hook expects anINT
orderID
.
[Woo Developer Blog]
PostgreSQL or MySQL: What Should I Choose for My Full-Stack Project?
Both MySQL and PostgreSQL are popular open-source databases, each fully ACID compliant. In truth, either of them will be a solid choice for your application.
However, for more complex projects, I would give the edge to PostgreSQL simply because of its extensibility. Especially anything spatial-related in which PostGIS can be used.
MySQL has widespread use and is a default component in the reliable, time-tested LAMP stack so it is a viable option as well.
[Hacker Noon]
[#Affiliates] - Your support keeps the OpenLampTech newsletter free for readers
Take your Laravel applications to the next level with Battle Ready Laravel by Ash Allen. Learn how to improve the performance, maintainability, and security of your Laravel projects in this e-book.
Ultimate Laravel Boilerplate to help other indie hackers deliver their SaaS in hours. Get started with LaraFast today!
Popups, newsletters, and abandoned carts. Use Omnisend with integrated email and SMS campaigns.
Thank you for reading. I hope you have a great rest of your week.
Take care.
Josh Otwell
OpenLampTech is a reader-supported publication. You can support the publication with a virtual coffee for as little as $3 (USD).