Month: April 2023

Discover new & useful Laravel packages. A place where you can find any Laravel package that you may need for your next project.Laravel News Links

https://cdn.arstechnica.net/wp-content/uploads/2023/04/dolly_hero-760×380.jpg

Ars Technica – All content

https://theawesomer.com/photos/2023/04/ultimate_ifixit_tool_kit_t.jpg

 | Buy

Fix all the things with iFixit’s professional-grade repair toolkit. It includes precision screwdrivers of all kinds, an antistatic mat, a magnetic repair workstation, suction cups, spudgers, tweezers, picks, an anti-clamp for pulling things apart, a digital multimeter, a digital caliper, and much more, all packed in a single bag.

The Awesomer

https://s3.us-east-1.amazonaws.com/images.gearjunkie.com/uploads/2023/04/Instinct2XSolar_HR_4001.55-copy-scaled.jpg

The Instinct 2X Solar ($450) is the newest addition to the Instinct family of Garmin smartwatches, and it has a feature that is so simple yet so genius. Yeah, yeah, yeah, it’ll stay charged forever so long as you get 3 hours of sunlight on its face — who cares? It has a flashlight.

Picture this: You’re a hunter. You hop out of your truck after driving for 2 hours, and it’s still 2 hours to daylight. Your headlamp is sitting in the snow in your driveway, where it landed after it fell out of your pack. You now either have to carefully trek across unstable terrain in the pitch blackness of night or drain your phone using the flashlight to illuminate your way.

I don’t have to picture it because I lived it. My cracked phone screen and now weak ankle are remnants of that mistake.

The Instinct 2X Solar smartwatch would have likely saved my bacon. Such a simple innovation: light.

This is just a first look at this new offering from Garmin, so we won’t dive too deep. We will be putting this watch through some serious testing, so stay tuned.

If we seem oddly excited about something as simple as a flashlight, just trust us when we say it’s a killer design feature that somehow doesn’t really exist in most modern smartwatches.

Outside of shedding light along your path, you can expect all of the bells and whistles. Wellness, fitness, and lifestyle tracking options will be plentiful. This watch is built rugged with a 50mm polymer case, topped with a power glass lens, which produces 50% more energy than the previous Instinct solar watch.

Instinct 2X Solar Battery Life

The battery life breakdown is pretty intense. We could try to explain it all or — we can just show you the specs:

• Smartwatch: 40 days; unlimited with solar*
• GPS: 60 hours; 145 hours with solar**
• All Satellite Systems: 40 hours; 65 hours with solar*
• All Satellite Systems + Multi-Band: 27 hours; 36 hours with solar**
• Max Battery GPS Mode: 150 hours; unlimited with solar**
• Expedition GPS Activity: 60 days; unlimited with solar*
• Battery Saver Watch Mode: 100 days; unlimited with solar*

*Solar charging, assuming all-day wear with 3 hours per day outside in 50,000-lux conditions
**Solar charging, assuming use in 50,000-lux conditions

The gist of all those numbers is this — it has a battery that will keep running long after your feet are sick of moving. So, long as you can get 3 hours of sun on your wrist, you can count on the watch to keep on ticking.

Instinct 2x Solar New Features of Note

Did we mention that this thing has a flashlight? It also is the first in the line to offer Obstacle Course Racing. It also comes in two different editions.

The Tactical Edition ($500) is built to U.S. military standards and offers features specific to a tactical environment, such as Jumpmaster and the ability to turn on Stealth Mode, which prevents the sharing of your GPS location.

Conclusion

We’re excited to get this watch into the field and tested. Check back to see if it lives up to our expectations and if we make it to our tree stand without breaking a leg.

The post Infinite Battery Life — And a Built-In Flashlight? Garmin Introduces the Instinct 2X Solar appeared first on GearJunkie.

GearJunkie

https://s3.us-east-1.amazonaws.com/images.gearjunkie.com/uploads/2023/04/Instinct2XSolar_HR_4001.55-copy-scaled.jpg

The Instinct 2X Solar ($450) is the newest addition to the Instinct family of Garmin smartwatches, and it has a feature that is so simple yet so genius. Yeah, yeah, yeah, it’ll stay charged forever so long as you get 3 hours of sunlight on its face — who cares? It has a flashlight.

Picture this: You’re a hunter. You hop out of your truck after driving for 2 hours, and it’s still 2 hours to daylight. Your headlamp is sitting in the snow in your driveway, where it landed after it fell out of your pack. You now either have to carefully trek across unstable terrain in the pitch blackness of night or drain your phone using the flashlight to illuminate your way.

I don’t have to picture it because I lived it. My cracked phone screen and now weak ankle are remnants of that mistake.

The Instinct 2X Solar smartwatch would have likely saved my bacon. Such a simple innovation: light.

This is just a first look at this new offering from Garmin, so we won’t dive too deep. We will be putting this watch through some serious testing, so stay tuned.

If we seem oddly excited about something as simple as a flashlight, just trust us when we say it’s a killer design feature that somehow doesn’t really exist in most modern smartwatches.

Outside of shedding light along your path, you can expect all of the bells and whistles. Wellness, fitness, and lifestyle tracking options will be plentiful. This watch is built rugged with a 50mm polymer case, topped with a power glass lens, which produces 50% more energy than the previous Instinct solar watch.

Instinct 2X Solar Battery Life

The battery life breakdown is pretty intense. We could try to explain it all or — we can just show you the specs:

• Smartwatch: 40 days; unlimited with solar*
• GPS: 60 hours; 145 hours with solar**
• All Satellite Systems: 40 hours; 65 hours with solar*
• All Satellite Systems + Multi-Band: 27 hours; 36 hours with solar**
• Max Battery GPS Mode: 150 hours; unlimited with solar**
• Expedition GPS Activity: 60 days; unlimited with solar*
• Battery Saver Watch Mode: 100 days; unlimited with solar*

*Solar charging, assuming all-day wear with 3 hours per day outside in 50,000-lux conditions
**Solar charging, assuming use in 50,000-lux conditions

The gist of all those numbers is this — it has a battery that will keep running long after your feet are sick of moving. So, long as you can get 3 hours of sun on your wrist, you can count on the watch to keep on ticking.

Instinct 2x Solar New Features of Note

Did we mention that this thing has a flashlight? It also is the first in the line to offer Obstacle Course Racing. It also comes in two different editions.

The Tactical Edition ($500) is built to U.S. military standards and offers features specific to a tactical environment, such as Jumpmaster and the ability to turn on Stealth Mode, which prevents the sharing of your GPS location.

Conclusion

We’re excited to get this watch into the field and tested. Check back to see if it lives up to our expectations and if we make it to our tree stand without breaking a leg.

The post Infinite Battery Life — And a Built-In Flashlight? Garmin Introduces the Instinct 2X Solar appeared first on GearJunkie.

GearJunkie

http://img.youtube.com/vi/uHGShqcAHlQ/0.jpg

Nintendo has shared one last trailer before The Legend of Zelda: Tears of the Kingdom arrives on May 12th, and this one is worth watching if you’re looking for some insight into the story. The rather lengthy clip showcases not only a large and varied world (including the floating islands above Hyrule), but Link’s allies. As Zelda makes clear, "you are not alone." There’s even a moment where Link offers a wagon ride.

The plot appears familiar — surprise, you’ll have to find Zelda and defeat Ganon. Instead, it’s the gameplay mechanics that promise to help Tears of the Kingdom set itself apart from Breath of the Wild. The skyborne islands factor play a large role, of course, but the reliance on fused-together weapons and vehicles is clearer in this new trailer. You can even build a ‘robot’ to take on Bokoblins that have their own battle platform.

The game is arriving alongside Tears-themed Pro Controller ($75) and Carrying Case ($25) accessories. You can also buy a special edition OLED Switch on April 28th for $350 if you’re new to the platform or itching to upgrade from an early-model console. As the hardware and flurry of trailers suggests, Nintendo wants to be sure you’re paying attention to the company’s most important game of the year.

This article originally appeared on Engadget at https://www.engadget.com/new-legend-of-zelda-tears-of-the-kingdom-trailer-shows-links-allies-144943398.html?src=rssEngadget

https://s3files.core77.com/blog/images/1396764_81_123024_liDPIa68J.jpg

If you’ve watched the movie "Air," you know that the release of the first Air Jordans reversed Nike’s then-declining sales, earning $126 million in their first year. Millions of people will see the movie. It’s a shame that this video below, about how sneakers are actually manufactured, has only been seen by a couple thousand people. Still, it’s worth a watch whether you’re an aspiring footwear designer or a sneakerhead.

This company isn’t manufacturing Air Jordans, of course, so there are some differences; whereas most modern sneakers feature molded soles, this company (Japan’s Spingle) has a repeating pattern on their soles, so they can actually extrude them in sheets. But you’ll still see plenty of modern-day relevant steps:

Core77

https://www.percona.com/blog/wp-content/uploads/2023/03/of_the_insides_of_a_dolphin_are_made_out_c3208efd-ea2b-44c3-98b2-797c9f5b1f5e-200×119.jpg

Indexes are crucial for optimizing query execution times in databases, but having an excessive number of indexes, or redundant ones, can negatively impact performance. While pt-duplicate-key-checker is the go-to tool for identifying duplicate or redundant indexes in MySQL, it may not catch all duplicates.

In this blog post, we’ll put ourselves to the test and see if we can identify duplicate and redundant indexes in MySQL. Toward the end, we will identify what the pt-duplicate-key-checker doesn’t.

The unique quiz

Consider the following MySQL table definition. Let’s put our brains to work and note any of the duplicate or redundant indexes (play fair, don’t cheat):

CREATE TABLE `table_with_lot_of_trouble` (
`id` int NOT NULL,
`col1` varchar(1) DEFAULT NULL,
`col2` varchar(2) DEFAULT NULL,
`col3` varchar(3) DEFAULT NULL,
`col4` varchar(4) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `id` (`id`),
UNIQUE KEY `col1` (`col1`,`col2`),
UNIQUE KEY `col2` (`col2`,`col1`),
UNIQUE KEY `col1_2` (`col1`,`col2`),
UNIQUE KEY `col1_3` (`col1`,`col2`,`col3`),
UNIQUE KEY `col1_4` (`col1`),
UNIQUE KEY `col1_5` (`col1`),
KEY `idx1` (`col1`,`id`),
KEY `idx2` (`col1`,`col2`),
KEY `idx3` (`col2`,`col1`),
KEY `idx4` (`col1`,`col2`,`col3`),
KEY `idx5` (`col1`,`col2`)
) ENGINE=InnoDB;

While you work on noting down the duplicate indexes in that MySQL table, let me also add some descriptions for duplicate and redundant indexes.

Duplicate index

Duplicate indexes occur when two or more indexes have the same set of columns in the same order. These can occur accidentally due to poor database design or through the use of database management tools that automatically create indexes without checking for duplicates.

Redundant index

Redundant indexes occur when two or more indexes have some overlapping columns. While these may not be exact duplicates, they can still negatively impact database performance.

Both duplicate and redundant indexes can waste disk space and slow down write operations. Each additional index requires additional disk space and inserts, so updates and deletes have to update multiple indexes. Additionally, such indexes can make it harder for the query optimizer to choose the most efficient index, as it has more options to consider.

Test results

Now, I believe you have your list of duplicate keys ready. Let us see what our favorite pt-duplicate-key-checker tells us about the indexes of the table, along with the reasons why they are considered duplicate or redundant.

[root@ip-172-31-82-182 ~]# pt-duplicate-key-checker --databases test --tables table_with_lot_of_trouble
# ########################################################################
# test.table_with_lot_of_trouble
# ########################################################################

# Uniqueness of id ignored because PRIMARY is a duplicate constraint
# id is a duplicate of PRIMARY
# Key definitions:
# UNIQUE KEY `id` (`id`),
# PRIMARY KEY (`id`),
# Column types:
# `id` int not null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `id`;

# Uniqueness of col1_4 ignored because col1_5 is a duplicate constraint
# col1_4 is a duplicate of col1_5
# Key definitions:
# UNIQUE KEY `col1_4` (`col1`),
# UNIQUE KEY `col1_5` (`col1`),
# Column types:
# `col1` varchar(1) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `col1_4`;

# idx3 is a duplicate of col2
# Key definitions:
# KEY `idx3` (`col2`,`col1`),
# UNIQUE KEY `col2` (`col2`,`col1`),
# Column types:
# `col2` varchar(2) default null
# `col1` varchar(1) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `idx3`;

# idx4 is a duplicate of col1_3
# Key definitions:
# KEY `idx4` (`col1`,`col2`,`col3`),
# UNIQUE KEY `col1_3` (`col1`,`col2`,`col3`),
# Column types:
# `col1` varchar(1) default null
# `col2` varchar(2) default null
# `col3` varchar(3) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `idx4`;

# Uniqueness of col1 ignored because col1_5 is a stronger constraint
# col1 is a left-prefix of col1_3
# Key definitions:
# UNIQUE KEY `col1` (`col1`,`col2`),
# UNIQUE KEY `col1_3` (`col1`,`col2`,`col3`),
# Column types:
# `col1` varchar(1) default null
# `col2` varchar(2) default null
# `col3` varchar(3) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `col1`;

# Uniqueness of col1_2 ignored because col1_5 is a stronger constraint
# col1_2 is a left-prefix of col1_3
# Key definitions:
# UNIQUE KEY `col1_2` (`col1`,`col2`),
# UNIQUE KEY `col1_3` (`col1`,`col2`,`col3`),
# Column types:
# `col1` varchar(1) default null
# `col2` varchar(2) default null
# `col3` varchar(3) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `col1_2`;

# idx2 is a left-prefix of col1_3
# Key definitions:
# KEY `idx2` (`col1`,`col2`),
# UNIQUE KEY `col1_3` (`col1`,`col2`,`col3`),
# Column types:
# `col1` varchar(1) default null
# `col2` varchar(2) default null
# `col3` varchar(3) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `idx2`;

# idx5 is a left-prefix of col1_3
# Key definitions:
# KEY `idx5` (`col1`,`col2`)
# UNIQUE KEY `col1_3` (`col1`,`col2`,`col3`),
# Column types:
# `col1` varchar(1) default null
# `col2` varchar(2) default null
# `col3` varchar(3) default null
# To remove this duplicate index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `idx5`;

# Key idx1 ends with a prefix of the clustered index
# Key definitions:
# KEY `idx1` (`col1`,`id`),
# PRIMARY KEY (`id`),
# Column types:
# `col1` varchar(1) default null
# `id` int not null
# To shorten this duplicate clustered index, execute:
ALTER TABLE `test`.`table_with_lot_of_trouble` DROP INDEX `idx1`, ADD INDEX `idx1` (`col1`);

# ########################################################################
# Summary of indexes
# ########################################################################

# Size Duplicate Indexes 145
# Total Duplicate Indexes 9
# Total Indexes 13

The pt-duplicate-key-checker notes nine duplicate indexes. Could you identify all nine of them? If so, surely you’ve good command over the database schema design. But I wouldn’t write a blog to test your compatibility with pt-duplicate-key-checker.

There is one more duplicate key that pt-duplicate-key-checker is missing; could you identify it? If so, I encourage you to apply at Percona and give me an opportunity to work with smarter brains.

The duplicate unique keys

For those who couldn’t identify the duplicate index, the unidentified duplicate keys are… (drum roll)…

UNIQUE KEY (col1, col2)
UNIQUE KEY (col2, col1)

It follows logically that if a tuple {a, b} is unique, then {b, a} will also be unique. Similar to how Peter Parker is to Spiderman and Gangadhar is to Shaktiman, the set {a, b} is equivalent to the set {b, a}.  This causes the unique key to double-enforce the uniqueness check.

Therefore, having an additional duplicate constraint defined on the same set of columns becomes unnecessary regardless of order. This is specifically true for two-column unique keys only. To optimize your database, you should consider dropping the second unique key or converting it to a secondary index if it is required.

Since you cannot go on and read all table definitions, I wrote a query for you to identify duplicate unique indexes:

mysql> SELECT DISTINCT TABLE_SCHEMA, TABLE_NAME, group_concat(INDEX_NAME) duplic8_UK, COLUMN_NAMES FROM 
 (SELECT DISTINCT TABLE_SCHEMA, TABLE_NAME, INDEX_NAME, GROUP_CONCAT(COLUMN_NAME ORDER BY COLUMN_NAME SEPARATOR ',') AS COLUMN_NAMES 
 FROM information_schema.STATISTICS WHERE NON_UNIQUE = 0 AND INDEX_NAME!='PRIMARY' AND INDEX_TYPE = 'BTREE'  
 GROUP BY TABLE_SCHEMA, TABLE_NAME, INDEX_NAME) X group by TABLE_SCHEMA, TABLE_NAME, COLUMN_NAMES having count(*)> 1;

+--------------+---------------------------------------------+---------------+--------------+
| TABLE_SCHEMA | TABLE_NAME | duplic8_UK | COLUMN_NAMES |
+--------------+---------------------------------------------+---------------+--------------+
| test | table_with_lot_of_trouble | col1_4,col1_5 | col1 |
| test | table_with_lot_of_trouble | col1,col2 | col1,col2 |
+--------------+---------------------------------------------+---------------+--------------+

Also, don’t forget to provide your opinion in the comments section: Should the non-identification issue with pt-duplicate-key-checker be considered a bug report or a feature request?

Conclusion

Percona’s pt-duplicate-key-checker is an amazing tool, but like every other tool, it is not “fool-proof.” While you create your indexes, evaluate them for duplicity.

Percona Distribution for MySQL is the most complete, stable, scalable, and secure open source MySQL solution available, delivering enterprise-grade database environments for your most critical business applications… and it’s free to use!

 

Try Percona Distribution for MySQL today!

Planet MySQL

https://i.kinja-img.com/gawker-media/image/upload/c_fill,f_auto,fl_progressive,g_center,h_675,pg_1,q_80,w_1200/322b2d7594a06eec134e3e47f5fb66a7.jpg

Lifehacker

https://lunarphp.io/og.jpgAn open-source package that brings the power of modern headless e-commerce functionality to Laravel.Laravel News Links