budni.testirovshika

QA #tester

[Code Geek @codek_tv]

Geometry Challenge: X = ?

[budni.testirovshika @DavronQA]

@HananyaNaftali You that mfuc*** hananya shit 💩

[budni.testirovshika @DavronQA]

@jakeshieldsajj Make world Islam again !!!

[budni.testirovshika @DavronQA]

@DravenNoctis Terrorists mfuckers

[Alex Xu @alexxubyte]

How is data sent over the internet? What does that have to do with the OSI model? How does TCP/IP fit into this?

7 Layers in the OSI model are:
1. Physical Layer
2. Data Link Layer
3. Network Layer
4. Transport Layer
5. Session Layer
6. Presentation Layer
7. Application Layer

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/uc5M7CdXXC

[Buitengebieden @buitengebieden]

Me trying to find the bathroom switch in the middle of the night.. 😂

[Nikki Siapno @NikkiSiapno]

Want to know the secret to optimizing your SQL queries?

Understanding the execution order is essential.

A SQL query executes its statements in the following order:

1. FROM / JOIN
2. WHERE
3. GROUP BY
4. HAVING
5. SELECT
6. DISTINCT
7. ORDER BY
8. LIMIT / OFFSET

𝗧𝗵𝗲 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀 𝘆𝗼𝘂 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗮𝘁 𝗲𝗮𝗰𝗵 𝘀𝘁𝗲𝗽 𝗵𝗲𝗹𝗽 𝘀𝗽𝗲𝗲𝗱 𝘂𝗽 𝘁𝗵𝗲 𝗳𝗼𝗹𝗹𝗼𝘄𝗶𝗻𝗴 𝘀𝘁𝗲𝗽𝘀. This is why it's important to know their execution order. 𝗧𝗼 𝗺𝗮𝘅𝗶𝗺𝗶𝘇𝗲 𝗲𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆, 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗶𝗻𝗴 𝘁𝗵𝗲 𝘀𝘁𝗲𝗽𝘀 𝗲𝗮𝗿𝗹𝗶𝗲𝗿 𝗶𝗻 𝘁𝗵𝗲 𝗾𝘂𝗲𝗿𝘆.

With that in mind, let's take a look at some 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝘁𝗶𝗽𝘀:

𝟭) 𝗠𝗮𝘅𝗶𝗺𝗶𝘇𝗲 𝘁𝗵𝗲 𝗪𝗛𝗘𝗥𝗘 𝗰𝗹𝗮𝘂𝘀𝗲

This clause is executed early, so it's a good opportunity to reduce the size of your data set before the rest of the query is processed.

𝟮) 𝗙𝗶𝗹𝘁𝗲𝗿 𝘆𝗼𝘂𝗿 𝗿𝗼𝘄𝘀 𝗯𝗲𝗳𝗼𝗿𝗲 𝗮 𝗝𝗢𝗜𝗡

Although the FROM/JOIN occurs first, you can still limit the rows. To limit the number of rows you are joining, use a subquery in the FROM statement instead of a table.

𝟯) 𝗨𝘀𝗲 𝗪𝗛𝗘𝗥𝗘 𝗼𝘃𝗲𝗿 𝗛𝗔𝗩𝗜𝗡𝗚

The HAVING clause is executed after WHERE & GROUP BY. This means you're better off moving any appropriate conditions to the WHERE clause when you can.

𝟰) 𝗗𝗼𝗻'𝘁 𝗰𝗼𝗻𝗳𝘂𝘀𝗲 𝗟𝗜𝗠𝗜𝗧, 𝗢𝗙𝗙𝗦𝗘𝗧, 𝗮𝗻𝗱 𝗗𝗜𝗦𝗧𝗜𝗡𝗖𝗧 𝗳𝗼𝗿 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀

It's easy to assume that these would boost performance by minimizing the data set, but this isn’t the case. Because they occur at the end of the query, they make little to no impact on its performance.

If you want to create efficient queries, it's a good idea to understand how things work under the hood otherwise your efforts may be wasted. While these tips work best in most cases, you should consider your unique use case when choosing the best course of action.

[budni.testirovshika @DavronQA]

@DrLoupis @bobomurod Yes! Guilty

[Zack Kanter @zackkanter]

it’s hard to imagine how it feels to be one of these journalists. the sick thrill of a hospital strike. the disappointment as the facts unfold against the narrative.

[Локальный диск D @bobomurod]

Новости для слепых и глухих которые не умеют гуглить и верят всему что льют им в ухо

[Buitengebieden @buitengebieden]

What is going on here? 😂

[budni.testirovshika @DavronQA]

@IsraelHamasNews Hitler destroy your nation and culture, and he was right!

[TESLA CARS ONLY⚡️ @teslacarsonly]

TESLA ROADSTER EQUIPPED WITH UFO THOR EXHAUST SOUNDS.

[Mobile Hacker @androidmalware2]

[New Blog] NetHunter Hacker IX

How to use MANA Toolkit to create Wi-Fi rogue access point to intercept HTTP traffic and prevent getting hacked
https://t.co/6ojaJHM7tE

[Massimo @Rainmaker1973]

Fishing knots

[The Figen @TheFigen_]

Partners in crime 😂

[budni.testirovshika @DavronQA]

@cb_doge Good job 👏

[Why you should have a cat @ShouldHaveCat]

This is how sleeping with a cat looks like

[Nature is Amazing ☘️ @AMAZlNGNATURE]

Bear startled by mirror reflection

[Apple Intro @appleintro]

iPhone 15 Pro concept in Deep Red 🥵