Nuffing.com

Every MySQL database programmer should learn and apply the newly added MariaDB and MySQL Window Functions and Common Table Expressions(CTEs) in their daily work. Both CTEs and window functions enable easy solutions to many query challenges that in prior releases have been difficult and sometimes impossible to surmount. Mastering these features opens the door to query solutions that are more robust, execute faster, and are easier to maintain over time than prior solutions using older techniques.

In our last blog we compared User Roles in MySQL 8 vs. MariaDB.  Today, we will here compare Window Functions and Common Table Expressions in both databases.

Window Functions

While all database administrators are familiar with aggregate functions like COUNT(), SUM(), and AVG(), far less people make use of window functions in their queries.  Unlike aggregate functions, which operate on an entire table, window functions operate on a set of rows and return a single aggregated value for each row.

The main advantage of using window functions over regular aggregate functions is that window functions do not cause rows to become grouped into a single output row.  Instead, the rows retain their separate identities and an aggregated value is added to each row.

Window Functions in MariaDB

Windowing functions were added to the ANSI/ISO Standard SQL:2003 and then extended in ANSI/ISO Standard SQL:2008.  DB2, Oracle, Sybase, PostgreSQL and other products have had full implementations for years. Other vendors added support for window functions later on.  Case in point, Microsoft did not add Window Functions to SQL Server until SQL 2012.

After numerous wishes and feature requests for window functions over the years, they were finally introduced in MariaDB 10.2.0 to great fanfare!  Now MariaDB includes window functions such as ROW_NUMBER, RANK, DENSE_RANK, PERCENT_RANK, CUME_DIST, NTILE, COUNT, SUM, AVG, BIT_OR, BIT_AND and BIT_XOR.

The Syntax

Window function queries are characterised by the OVER keyword, following which the set of rows used for the calculation is specified. By default, the set of rows used for the calculation (the “window”) is the entire dataset, which can be ordered with the ORDER BY clause. The PARTITION BY clause is then employed to reduce the window to a particular group within the dataset.

Here’s an example:
Given the following table of student test scores:

+------------+---------+--------+
| name       | test    | score  |
+------------+---------+--------+
| Steve      | SQL     | 75     |
+------------+---------+--------+
| Robert     | SQL     | 43     |
+------------+---------+--------+
| Tracy      | SQL     | 56     |
+------------+---------+--------+
| Tatiana    | SQL     | 87     |
+------------+---------+--------+
| Steve      | Tuning  | 73     |
+------------+---------+--------+
| Robert     | Tuning  | 31     |
+------------+---------+--------+
| Tracy      | Tuning  | 88     |
+------------+---------+--------+
| Tatiana    | Tuning  | 83     |
+------------+---------+--------+

The following two queries return the average test scores partitioned by test and by name respectively – in other words, aggregated by test and by name:

SELECT name, test, score, AVG(score) OVER (PARTITION BY test) 

  AS average_by_test FROM test_scores;

+----------+--------+-------+-----------------+
| name     | test   | score | average_by_test |
+----------+--------+-------+-----------------+
| Steve    | SQL    |    75 |         65.2500 |
| Steve    | Tuning |    73 |         68.7500 |
| Robert   | SQL    |    43 |         65.2500 |
| Robert   | Tuning |    31 |         68.7500 |
| Tracy    | SQL    |    56 |         65.2500 |
| Tracy    | Tuning |    88 |         68.7500 |
| Tatiana  | SQL    |    87 |         65.2500 |
| Tatiana  | Tuning |    83 |         68.7500 |
+----------+--------+-------+-----------------+

SELECT name, test, score, AVG(score) OVER (PARTITION BY name) 

  AS average_by_name FROM student;

+---------+--------+-------+-----------------+
| name    | test   | score | average_by_name |
+---------+--------+-------+-----------------+
| Steve   | SQL    |    75 |         74.0000 |
| Steve   | Tuning |    73 |         74.0000 |
| Robert  | SQL    |    43 |         37.0000 |
| Robert  | Tuning |    31 |         37.0000 |
| Tracy   | SQL    |    56 |         72.0000 |
| Tracy   | Tuning |    88 |         72.0000 |
| Tatiana | SQL    |    87 |         85.0000 |
| Tatiana | Tuning |    83 |         85.0000 |
+---------+--------+-------+-----------------+

In both cases, note that the original scores are still available to each row.

Window Functions in MySQL 8

MySQL has been even later in adopting the Window Functions standard, with it being part of version 8.0 that is expected to be released later this year.   

MySQL employs the same ANSI/ISO Standard as other DBMSes whereby Window function queries are characterised by the OVER keyword and the PARTITION BY clause is employed to reduce the window to a specific group within the result set.

The currently supported functions include:

Name	Description
CUME_DIST()	Cumulative distribution value
DENSE_RANK()	Rank of current row within its partition, without gaps
FIRST_VALUE()	Value of argument from the first row of window frame
LAG()	Value of argument from row lagging current row within partition
LAST_VALUE()	Value of argument from the last row of window frame
LEAD()	Value of argument from row leading current row within partition
NTH_VALUE()	Value of argument from N-th row of window frame
NTILE()	Bucket number of the current row within its partition.
PERCENT_RANK()	Percentage rank value
RANK()	Rank of current row within its partition, with gaps
ROW_NUMBER()	Number of current row within its partition

As an example, we’ll explore the CUME_DIST() function.

It returns the cumulative distribution of a value within a group of values; that is, the percentage of partition values less than or equal to the value in the current row. This represents the number of rows preceding or peer with the current row in the window ordering of the window partition divided by the total number of rows in the window partition. Return values range from 0 to 1.

This function is usually used with ORDER BY to sort partition rows into the desired order. Without ORDER BY, all rows are peers having a value of 1.

The following query shows, for the set of values in the val column, the CUME_DIST() value for each row, as well as the percentage rank value returned by the similar PERCENT_RANK() function. For reference, the query also displays row numbers using ROW_NUMBER():

SELECT

  val,

  ROW_NUMBER()   OVER w AS 'row_number',

  CUME_DIST()    OVER w AS 'cume_dist',

  PERCENT_RANK() OVER w AS 'percent_rank'

FROM numbers

WINDOW w AS (ORDER BY val);

+------+------------+--------------------+--------------+
| val  | row_number | cume_dist          | percent_rank |
+------+------------+--------------------+--------------+
|    1 |          1 | 0.2222222222222222 |            0 |
|    1 |          2 | 0.2222222222222222 |            0 |
|    2 |          3 | 0.3333333333333333 |         0.25 |
|    3 |          4 | 0.6666666666666666 |        0.375 |
|    3 |          5 | 0.6666666666666666 |        0.375 |
|    3 |          6 | 0.6666666666666666 |        0.375 |
|    4 |          7 | 0.8888888888888888 |         0.75 |
|    4 |          8 | 0.8888888888888888 |         0.75 |
|    5 |          9 |                  1 |            1 |
+------+------------+--------------------+--------------+

The OVER clause is permitted for many aggregate functions, including:

• AVG()
• COUNT()
• MAX()
• MIN()
• STDDEV_POP(), STDDEV(), STD()
• STDDEV_SAMP()
• SUM()
• VAR_POP(), VARIANCE()
• VAR_SAMP()

These can be used as window or non-window functions, depending on whether the OVER clause is present or absent:

MySQL also supports non-aggregate functions that are used only as window functions. For these, the OVER clause is mandatory:

• CUME_DIST()
• DENSE_RANK()
• FIRST_VALUE()
• LAG()
• LAST_VALUE()
• LEAD()
• NTH_VALUE()
• NTILE()
• PERCENT_RANK()
• RANK()
• ROW_NUMBER()

As an example of a non-aggregate window functions, this query uses ROW_NUMBER(), which produces the row number of each row within its partition. In this case, rows are numbered per country. By default, partition rows are unordered and row numbering is indeterminate. To sort partition rows, include an ORDER BY clause within the window definition. The query uses unordered and ordered partitions (the row_num1 and row_num2 columns) to illustrate the difference that omitting and including ORDER BY makes:

SELECT

  year, country, product, profit,

  ROW_NUMBER() OVER(PARTITION BY country) AS row_num1,

  ROW_NUMBER() OVER(PARTITION BY country ORDER BY year, product) AS row_num2

FROM sales;

+------+---------+------------+--------+----------+----------+
| year | country | product    | profit | row_num1 | row_num2 |
+------+---------+------------+--------+----------+----------+
| 2000 | Finland | Computer   |   1500 |        2 |        1 |
| 2000 | Finland | Phone      |    100 |        1 |        2 |
| 2001 | Finland | Phone      |     10 |        3 |        3 |
| 2000 | India   | Calculator |     75 |        2 |        1 |
| 2000 | India   | Calculator |     75 |        3 |        2 |
| 2000 | India   | Computer   |   1200 |        1 |        3 |
| 2000 | USA     | Calculator |     75 |        5 |        1 |
| 2000 | USA     | Computer   |   1500 |        4 |        2 |
| 2001 | USA     | Calculator |     50 |        2 |        3 |
| 2001 | USA     | Computer   |   1500 |        3 |        4 |
| 2001 | USA     | Computer   |   1200 |        7 |        5 |
| 2001 | USA     | TV         |    150 |        1 |        6 |
| 2001 | USA     | TV         |    100 |        6 |        7 |
+------+---------+------------+--------+----------+----------+

Common Table Expressions (CTEs)

A common table expression (CTE) can be thought of as a temporary result set that is defined within the execution scope of a single SELECT, INSERT, UPDATE, DELETE, or CREATE VIEW statement. A CTE is similar to a derived table in that it is not stored as an object and lasts only for the duration of the query. However, unlike a derived table, a CTE can be self-referencing and can be referenced multiple times in the same query.

A CTE can be used to:

• Create a recursive query.
• Substitute for a view when the general use of a view is not required; that is, you do not have to store the definition in metadata.
• Enable grouping by a column that is derived from a scalar subselect, or a function that is either not deterministic or has external access.
• Reference the resulting table multiple times in the same statement.

Using a CTE offers the advantages of improved readability and ease in maintenance of complex queries. The query can be divided into separate, simple, logical building blocks. These simple blocks can then be used to build more complex, interim CTEs until the final result set is generated.

Recursive CTEs

Recursive common table expressions (CTEs) were an implementation of standard SQL:1999 for hierarchical queries.  The first implementations of Recursive CTEs began appearing in 2007. The recursive CTEs from the standard were relatively close to the existing implementation in IBM DB2 version 2.  Recursive CTEs were eventually supported by Microsoft SQL Server (since SQL Server 2008 R2), Firebird 2.1, PostgreSQL 8.4+, SQLite 3.8.3+, Oracle 11g Release 2, and IBM Informix version 11.50+.

Without Common-table-expressions or a connected-by clause it is still possible to achieve hierarchical queries with user-defined recursive functions, but these tend to result in very complex SQL.

CTEs in MariaDB

In MariaDB, a non-recursive CTE is basically considered to be a query-local VIEW whose syntax is more readable than nested FROM (SELECT …). A CTE can refer to another and it can be referenced from multiple places.

Thus, CTEs are similar to derived tables. For example,

SQL with derived table:

SELECT * FROM

   ( SELECT * FROM employees

     WHERE dept = 'Engineering' ) AS engineers

WHERE
...

SQL with CTE:

WITH engineers AS
 
   ( SELECT * FROM employees

     WHERE dept = 'Engineering' )

SELECT * FROM engineers

WHERE ...

SQL is generally poor at recursion.  One of the advantages of CTEs is that they permit a query to reference itself, hence recursive SQL. A recursive CTE will repeatedly execute subsets of the data until it obtains the complete result set. This makes it particularly useful for handling hierarchical or tree-structured data.

With recursive CTEs you can achieve things that would be very difficult to do with standard SQL and at a faster execution speed. They can help solve many types of business problems and even simplify some complex SQL/application logic down to a simple recursive call to the database.

Some example uses for recursive CTE are to find gaps in data, create organization charts and create test data.

WITH RECURSIVE signifies a recursive CTE. It is given a name, followed by a body (the main query) as follows:

Below is a recursive CTE that counts from 1 to 50.
WITH   cte

AS     (SELECT 1 AS n -- anchor member

        UNION ALL

        SELECT n + 1 -- recursive member

        FROM   cte

        WHERE  n < 50 -- terminator
       )

SELECT n

FROM   cte;

The above statement prints a number series from 1 to 49.

CTEs in MySQL

MySQL 8.0 adds CTEs via the standard WITH keyword, in much the same way it is implemented in competing products.

To specify common table expressions, use a WITH clause that has one or more comma-separated subclauses. Each subclause provides a subquery that produces a result set, and associates a name with the subquery. The following example defines CTEs named cte1 and cte2 in the WITH clause, and refers to them in the top-level SELECT that follows the WITH clause:

WITH

  cte1 AS (SELECT a, b FROM table1),

  cte2 AS (SELECT c, d FROM table2)

SELECT b, d FROM cte1 JOIN cte2

WHERE cte1.a = cte2.c;

Immediately preceding SELECT for statements that include a SELECT statement:

• INSERT … WITH … SELECT …
• REPLACE … WITH … SELECT …
• CREATE TABLE … WITH … SELECT …
• CREATE VIEW … WITH … SELECT …
• DECLARE CURSOR … WITH … SELECT …
• EXPLAIN … WITH … SELECT …

A recursive common table expression is one having a subquery that refers to its own name. For example:

WITH RECURSIVE cte (n) AS

(
  SELECT 1

  UNION ALL

  SELECT n + 1 FROM cte WHERE n < 5
)

SELECT * FROM cte;

+------+
| n    |
+------+
|    1 |
|    2 |
|    3 |
|    4 |
|    5 |
+------+

Conclusion
Window Functions and Common Table Expressions (CTEs) have been a mainstay of many popular database products for some time now.  With the release of MySQL version 8 and MariaDB 10.2.0, both vendors have caught up with competing DBMSes such as SQL Server and Oracle.

The post Comparison of Window Functions & CTEs in MySQL 8 vs MariaDB appeared first on SQLyog Blog.

via Planet MySQL
Comparison of Window Functions & CTEs in MySQL 8 vs MariaDB

Arizona -(Ammoland.com)- The natural right to bear arms includes the right to carry them concealed as well as openly. Both types of carry were practiced at the time of the ratification of the Bill of Rights. Flintlock “muff pistols” were widely available before 1791. Daggers, dirks and other assorted blades were commonly carried concealed. Sword canes conceal the blade inside of the cane, and are considered concealed weapons. They were commonly available.  They became popular, in part, to avoid any social reproach against the carry of swords, anticipating the condemnation of open carry today.

The Second Amendment does not differentiate between concealed and openly carried arms.  Such differentiation was not discussed during the debates about the Second Amendment.  It was decades after the Bill of Rights was ratified that concealed carry was questioned. Arms technology had not changed significantly.

Concealed weapons had and have military purposes. General Gage, the British Officer in charge of occupied Boston, had his officers conceal their sidearms when patrolling to prevent Paul Revere’s ride. From William Diamond’s Drum page 94:

And finally, unbeknown to him. Gage had that afternoon posted mounted officers, with their sidearms concealed as though they were on pleasure jaunts, along the Cambridge roads, just in case messengers should try to give out alarms that night.

There were no colonial statutes that separated the carrying of concealed weapons from the open carrying of weapons.

The Kentucky legislature passed a statute forbidding concealed arms in 1813. It was challenged in court.

The statute was found unconstitutional in Bliss v. Commonwealth of Kentucky, in the state Supreme Court. It was 1822, three decades after the Second Amendment was ratified.  Any restriction on bearing arms was contrary to “the right of the citizens to bear arms in defense of themselves and the state“, and was therefore void.

The court reasoned that any diminution of the right that existed when the Constitutional protection was adopted, was an infringement of the right, and was therefore unconstitutional. The logic is impeccable.

In 1833, the Supreme Court ruled that the Bill of Rights, including the Second Amendment, did not apply to the states.

In 1833, the Indiana Supreme Court ruled that concealed carry could be banned for people who were not travelers.

Five other state courts, with different state constitutions,  (Alabama, Tennessee, Arkansas, Georgia, and Louisiana), ruled their legislatures could ban concealed carry  from 1833 to 1850, to varying degrees.

In Kentucky, a Constitutional amendment was deemed necessary. The constitutional amendment to allow the legislature to regulate the concealed carry of weapons passed in 1849, as part of a constitutional convention. In 1850, the wording in bold was added:

  “That the rights of the citizens to bear arms in defense of themselves and the State shall not be questioned; but the General Assembly may pass laws to prevent persons from carrying concealed arms.”

All but Indiana were slave states.  Prohibiting the carry of concealed weapons is particularly important to keeping suspect minorities disarmed.  If the weapons are concealed, it is much harder to enforce legal or extralegal disarmament techniques, such as selective enforcement under color of law.

In 1859,  The Texas Supreme Court, in Cockrum v. state, held that “The right of a citizen to bear arms, in defense of himself or the State, is absolute.”  The court cited both the Second Amendment and the then current Texas Constitution. The case held that if inexpensive weapons were prohibited, the right of self defense would be chilled for poor people.

In 1868 the Fourteenth Amendment was passed to assure, in part, that the Second Amendment would be enforced to insure that freed slaves could keep and bear arms. The former slave states found ways to evade the requirement. In 1873, the Fourteenth Amendment’s enforcement of the Bill of Rights against state encroachment was nullified by the Supreme Court.

In 1903, the Vermont Supreme Court, in State v. Rosenthal, found that an ordinance requiring a permit to carry a concealed pistol “..repugnant to the Constitution and laws of the state,”.

Federal laws have never been passed against the carry of concealed weapons.

In 2008 the Heller decision made clear what it meant to bear arms. Scalia quoted Justice Ginsburg’s writing in a previous case.  From cornell.edu:

Justice Ginsburg wrote that “[s]urely a most familiar meaning is, as the Constitution’s Second Amendment … indicate[s]: ‘wear, bear, or carry … upon the person or in the clothing or in a pocket, for the purpose … of being armed and ready for offensive or defensive action in a case of conflict with another person.’ ”

“..in the clothing or in a pocket” is carrying concealed.

Justice Scalia concluded that laws banning the concealed carry of arms were constitutional, solely because such laws were long standing in a number of states. Such laws were not upheld before the 1830’s, 40 years after the Bill of Rights was ratified.

Laws against the concealed carry of weapons are vestiges of laws designed to keep slaves and free blacks disarmed.

In 2010, the Supreme Court held the Second Amendment is incorporated against the States by the Fourteenth Amendment, finally doing what the Court should have done in 1873.

Adam Winkler, an Constitutional scholar at UCLA, has written that allowing only open carry may be the best way to discourage bearing arms in general.  He made the case this might be the most effective way for the California legislature to chill the exercise of the Second Amendment.

Vermont has never required a permit for open or concealed carry. Twelve states have reformed their laws to allow the carrying of weapons, concealed or openly, without permission from the government, since 2003. They call it Constitutional Carry.

Both open carry and concealed carry are protected by the Second Amendment. Restricting the bearing of arms to either open carry or  concealed carry is a clear infringement of that right to bear arms.

©2018 by Dean Weingarten: Permission to share is granted when this notice is included.

Link to Gun Watch

---

About Dean Weingarten:

Dean Weingarten has been a peace officer, a military officer, was on the University of Wisconsin Pistol Team for four years, and was first certified to teach firearms safety in 1973. He taught the Arizona concealed carry course for fifteen years until the goal of constitutional carry was attained. He has degrees in meteorology and mining engineering, and recently retired from the Department of Defense after a 30 year career in Army Research, Development, Testing, and Evaluation.

This post Open and Concealed Carry are Protected by the Second Amendment appeared first on AmmoLand.com .

via AmmoLand.com
Open and Concealed Carry are Protected by the Second Amendment

Sometimes you don’t want to just carry a pocket pistol.

Instead, you want to be able to feel the weight of that 1911 as you walk around, and hear it clunk on your nightstand when you take it off for the evening.

You just want to carry something big.

Now when most people think “big gun,” they think 1911 or a long barrel revolver, but unless you’re the Joker, you probably aren’t going to carry a Smith & Wesson 500 Magnum with the 6.5-inch barrel or a full-size Desert Eagle.

Instead, you might want to carry a Glock 17, H&K VP9, Kimber Stainless II 1911, or something similar.

While some of these have shorter barrels than others, they are all full-size guns, and none of them are small.

Of course, carrying a bigger gun brings a different set of challenges that you face when you carry a subcompact or even a compact handgun.

To help you out, this article is going to go over some of the things you’ll want to consider when you are thinking about or having trouble carrying a big gun.

Now, as you read below, it may come across like carrying a big gun is not a good idea.  That’s not the case at all; it’s totally up to you what you carry.

I do, however, want to discuss the pitfalls of carrying a big gun so you are aware of them before you go out and spend 1200 dollars on a sweet 1911 and realize you can’t appendix carry it like you saw in a movie.

So let’s get started.

Size Matters

Let’s compare some guns so you can see the size difference.

Compared to something like the Sig P238 in .380, a standard 1911 is 3.4 inches longer and almost twice as thick.  Even compared to a Glock 36 (their .45 ACP subcompact) you aren’t gaining much other than more gun to carry around.

Is one round worth hauling around the extra 15.5 ounces?  That’s almost an extra pound… for one bullet.

So what do we gain with the bigger gun?

For starters, you get a slightly larger round if you go with a 9mm version of the Kimber.  But, if you are carrying a 1911, most wouldn’t bother with 9mm and instead, go with the .45 ACP. This gives you a much larger round, obviously.

So yeah, you get one more bullet with the .45 ACP version, but the gun is almost twice as wide.  It’s even wider than the Glock 36 which is 1.10 inches wide and holds 6+1 rounds also.

Carry Positions for a Large CCW

Now that you know what you’re getting into, let’s talk carry positions for your big CCW gun.  Your carry position will greatly depend on your body type.

For example, if you are 5’11” and weigh 180 pounds, you’re more limited than a guy who’s 6’5” and 280 pounds.

Of course, your clothing choices will also play a large part how and where you carry a big CCW gun.

Do you wear tee shirts all the time?

Do you wear a jacket and dress pants?

A smaller frame pistol will be easier to conceal in the summer and in thinner, tighter fitting clothing.

Furthermore, your full-sized gun isn’t something you’ll want to carry in an ankle holster or even appendix carry.  It’s not going to be comfortable and is unlikely to even fit in the first place.

All that said, let’s look examine what options you do have.

Wear a Jacket

Depending on the occasion, you could wear a jacket.  This would allow for an OWB holster anywhere from the 3-6 o’clock position.  Most jackets will easily hide even a full-size gun in a holster.

Plus, even if you are able to comfortably carry your sidearm of choice in an IWB holster, adding another layer of loose-fitting clothing will help you ensure that you won’t print.

If you do choose to use an OWB holster, be sure not to keep it in a spot where it can easily be accidentally exposed.

Making sure your gun isn’t an attention grabber will also help.  If you have a nickel plated something or other with a mural painted on the slide, it’s going to be a lot easier to spot if your jacket opens in the wind.

Black gun, black holster, black pants; even a darker shirt helps.  And, of course, just keeping your jacket zipped or buttoned makes a huge difference.  If black isn’t your thing…check out our Gray Man Loadout.

Shoulder Holster

A shoulder holster is an alternative to a waistband holster if you are wearing a jacket.

This kind of holster isn’t for everyone though.  Those of us who have a thinner build might need to position the holster more to the vertically to hide the gun.

Regardless, the barrel could poke at the rear of your jacket or the grip might print out the front.

When holstering your gun under your arm, make sure you practice your draw. If you aren’t accustomed to it, you may fumble or have an otherwise difficult time if you need to pull your gun under pressure. This also goes for t-shirt holsters.

Inside the Waistband Holster

An IWB holster is also an option.  Like a shoulder holster, using a holster inside your waistband will really depend on your body-type.

You will also need to make sure you wear the appropriate clothing to conceal your gun.  A tuckable holster can help when you aren’t wearing a jacket or some other outer layer like a sweatshirt.

The position of your carry will also greatly depend on your body shape.  If you are on the leaner side, you will probably need to carry at the 4 or 5 o’clock position.

If you have a little more mass to you, the 3 o’clock position might be easier for you to hide and still draw your gun easily if you need it.

We can help you find the right IWB holster for you in our Best Concealed Carry Holsters review.

Final Thoughts

When you choose the gun you are going to carry every day to protect yourself, you need to make sure you can handle it well, so be sure to consider why you want to choose a large CCW weapon.

I prefer to carry for safety, but don’t like to have the inconvenience of a large gun where I need to change the way I bend or move or wear different clothing.

On the other hand, some people prefer the feeling of security that goes with a weightier weapon or feels more confident carrying a larger caliber.

Looking for more options? You should take a look at our other Best CCW Guns articles, we’ve looked at a huge range of guns from full-size to revolvers to subcompacts.

What about you?  What’s your CCW sidearm of choice?  What are your thoughts on big guns for CCW?  Have any advice for those looking for concealed carry larger sidearms?  As always, share your thoughts in the comments!

The post How to Concealed Carry a Full-Size (Or Even Larger) Gun appeared first on Pew Pew Tactical.

via Pew Pew Tactical
How to Concealed Carry a Full-Size (Or Even Larger) Gun

via Planet MySQL
New Webinar on How to Design Open Source Databases for High Availability

via TechCrunch
Now you can visit Disney Parks in the US through Google Street View

via Engadget
Google adds Disney parks to Street View

via Buckeye Firearms Association
Researchers: Schools are safer than they were in the 90s, and school shootings are not more common than they used to be

via Bearing Arms
Why Gun-Control Fails Miserably

Netflix announced today that it will soon be rolling out a new tool for parents. Already, parents can manage what their kids watch by putting all content above a particular maturity level behind a PIN or by marking which accounts belong to a child. But soon, parents will also be able to require a PIN for certain shows or movies. This way, parents won’t have to block full levels of content if they don’t want to and can instead just keep their children from watching certain titles. Additionally, maturity level ratings will also be displayed more noticeably on the screen when a new title begins playing.

Netflix’s changes come as a number of companies are working to make their platforms more child-appropriate. Apple plans to introduce more parental controls to its devices in the near future and YouTube recently had to deal with some disturbing content that was parading as kid-friendly. Gadgets geared towards children have also come under scrutiny as privacy concerns mount and Facebook’s new Messenger Kids app has attracted criticism for encouraging kids to spend more time on digital devices.

Netflix says its new controls will be rolling out in the coming months and that it’s also looking into how to make maturity level ratings more descriptive and easier to understand.

Via: VentureBeat

Source: Netflix

via Engadget
Netflix will let parents block individual movies and shows

Parents worried their kids will consume some unseemly content on Netflix have been able to block all the content that falls under a particular rating. Now, Netflix’s latest update gives you a little more control, allowing you to prevent your young viewer from watching particular programs you deem unsuitable for them, even if it falls in your selected ratings range. Not everyone wants their kid watching Stranger Things, no matter how many games of D&D they play. To keep them away from questionable content, all you need is a PIN and a list of movies you don’t want your child to see.

Add a PIN, Add Some Banned Movies

Go to Netflix to visit your account page and select the Parental Controls link. Enter your password and choose a PIN, which you’ll need to unlock the restrictions should you want to watch a previously restricted title. From there you can drag the rating slider from “Little Kids” to “Adults” and restrict by maturity level. If you just want to restrict a few particular movies and don’t want to put an entire category of films off-limits, you can add the name of the show or movie you want to block under the Restrict Specific Titles section.

Netflix also made it easier to figure out a movie’s rating before that first channel-changing scene. Now, when you start a show, you’ll see the film rating prominently displayed in the corner. Reconsidering your viewing ban on a few programs? Just enter the PIN when you select the banned title.

via Lifehacker
Activate Netflix’s New Parental Controls