As spring approaches, the Appleseed trail will soon start back up and we will begin building another group of Riflemen here in Ohio.
For those who don’t know about the Appleseed Project, we are a national 501(c)(3) non-profit organization that teaches the fundamentals of rifle marksmanship and combines this with a series of presentations on our shared heritage as Riflemen and Riflewomen.
Appleseed started thirteen years ago with the goal to reawaken America to the fading art of rifle marksmanship. We do that by teaching the fundamentals of field marksmanship and by sharing with our attendees the story of April 19, 1775.
Paul Revere’s ride, the events on Lexington Green, the engagement at the North Bridge, all have profound lessons for all of us on our shared marksmanship heritage and the price of liberty. Attending an Appleseed event will reacquaint you with our shared heritage and provide you with the rifle skills necessary to pass this heritage on to the next generation.
Our two-day events are staffed by skilled instructors who will share with you the skills needed to consistently hit targets out to 500 yards. Bring what you want to shoot. Open sights, scopes, centerfire or rim fire, we work with what our students bring.
Most of our work is done at 25 meters. Saturday at an Appleseed is heavy on instructions and drills. All this leads up to the Appleseed Qualification Test, the infamous AQT.
Our AQTs are a four-stage test to challenge your skills. We put you under some time pressure and ask you to execute 40 shots on targets that simulate ranges from 100-400 yards. It takes 210 points out of a possible 250 for you achieve your Rifleman’s patch and to leave with the pride of knowing that you are carrying on the great American Rifleman tradition.
Our events are open to all regardless of your skill levels. Youth are welcome as long as they can be safe on our line. We have worked with attendees from 8 to 80. Whether you are new to rifle marksmanship or are looking for a tune-up on your skills, we encourage you to join us for a weekend.
I can guarantee you will leave with a new appreciation for your skills, your country and the value of liberty.
Our 2020 schedule is available at appleseedinfo.org and we encourage you to come check us out. If you have any questions, feel free to contact me at ohio@appleseedinfo.org.
All of us at Appleseed would like to thank the Buckeye Firearms Association for supporting our program.
In ALTER TABLE for UUID we discuss currently proper way to store and handle UUID in MySQL. Currently it works, even in a performant way, but it still hurts. It should not.
Definition of UUID
The RFC 4122 defines various types of UUID, and how they are being formatted for presentation and as a bit field on the wire. As this document was written bei Leach and Salz, among others, RFC 4122 UUIDs are also called “Leach-Salz UUIDs” (for example in the Java Documentation).
There are other UUID variants, used in other systems (NCS, and Microsoft “backwards compatibility”).
A RFC 4122 UUID is a special 128 bit long value (“16 octets”). It is supposed to be laid out like this:
The high bits in clk_seq_hi_res define the variant, and anything starting with the bit sequence 10 is a RFC 4122 compliant UUID.
The high nibble in time_hi_and_version defines the RFC 4122 Type (or version), the algorithm used. RFC 4122 itself defines versions 1 to 5 (version 0 is unused).
There is an expired draft that defines a version 6, which is specifically designed to use a primary key for databases. It uses the same timestamp value as Type 1, but stores the bytes so that ordering by creation time is preserved. It also relaxes the requirements on the node field, officially allowing different sources for bits than the MAC address. Sample implementations are available in various languages.
UUIDs are all over the place in Windows and also in Java. Databases have to handle them as “application generated primary keys”. That’s why they are important and should be treated with some attention.
Handling UUID in MySQL 8
MySQL provides functions to generate UUIDs, to check if a thing is a validly formatted string that looks like a UUID, and to convert UUIDs to 128 bit bitstrings and back.
The latter two functions have a special flag to improve performance with InnoDB. This flag is by default off. No attempt is made to automatically do the right thing dependent on the UUID type.
UUID function
The MySQL function UUID() returns a RFC 4122 Type 1 UUID.
Formatted like in the RFC, we get the following values:
80462D3C
96AB 1 1EB
9 4 BB B A22
78F258E1
Specifically, the clk_seq_hi_res contains the variant value, 9, and the time_hi_and_version contains the version, 1.
According to the RFC, the variant9 = 1001 = 10x (a RFC 4122 compliant UUID).
Of the Versions defined in RFC 4122, it is Version 1 or Type 1, “The time-based version in this document”. The generation algorithm is defined in section 4.2 of that RFC.
So a MySQL generated UUID is always a RFC 4122 Type 1 (time based) UUID.
We have randomUUID(), returning a Type 4 UUID and nameUUIDFromBytes() for Type 3 and a generic Constructor that takes any 128 bit value. So what we get from Java is likely name based or random UUIDs generated by the application.
Name based UUIDs are fixed for a fixed name, so they pose no problem when used with MySQL as a primary key.
Random UUIDs are completely random. There is nothing to optimize for MySQL here.
Neither is a good choice to use as a kind of application controlled distribiuted primary key.
Based on the reasoning in ALTER TABLE for UUID, Java developers that are using UUID for this purpose would be well advised to implement and use a Type 1 UUID. It seems that such an implementation is not available by default as part of java.lang.util, but other implementations exist.
IS_UUID() function
The IS_UUID() predicate returns 1 for all strings that can be parsed as a UUID.
That is, it checks for one of three ways to write the UUID, and that it contains only valid hex digits in the places that actually contain data. No attempt is made to validate any of the bits. Code is here, and the actual parsing happens here.
UUID_TO_BIN() function
MySQL allows three ways to write UUIDs, as a 128 bit hex string (6ccd780cbaba102695645b8c656024db), as a 128 bit hex string with dashes in the right places (6CCD780C-BABA-1026-9564-5B8C656024DB) and as a 128 bit hex string with dashes in the right places and enclosed in curly braces ({6CCD780C-BABA-1026-9564-5B8C656024DB}).
This is not a particular dense packing of data for storage. The UUID_TO_BIN() function takes any of these strings and returns a VARBINARY(16) for storage.
The function has an optional second parameter, the swap_flag. When applied to a Type 1 UUID, the time bytes are being swapped around so that chronological ascending UUIDs from the same node are also having numerically ascending values. This optimizes storage with InnoDB.
Type 1 UUID: It is recommended you define UUID columns as VARBINARY(16) and use theUUID_TO_BIN(uuid_string, 1) function to store data.
Type 6 UUID: You should use UUID_TO_BIN(uuid_string, 0) to store Type 6 UUIDs, because Type 6 has been specifically created to avoid the swapping of time bytes around.
Other types: These do not profit from swapping, so also use UUID_TO_BIN(uuid_string, 0).
BIN_TO_UUID function
The inverse function to UUID_TO_BIN is BIN_TO_UUID(). It needs the same swap_flag value as has been used at write time in order to unpack the data correctly.
It should hurt less
This all should hurt less.
MySQL should have a native UUID column type, which stores data internally in a VARBINARY(16) (or BINARY(16)).
It should accept all three notations as input (hex string, with dashes, with curly braces and dashes). It should return a hex string without dashes or curlies.
It should validate variant and type (version), allowing Types 1 to 6.
It should auto-convert (swap) data for Type 1, but not for any other type.
There should be a formatting function that turns a hex string without dashes into a UUID string with dashes, or a UUID string with dashes and curlies.
and internally, this is stored as 0x1026BABA6CCD780C95645B8C656024DB, because variant is RFC 4122 and Type is 1.
For any other Type of the RFC 4122 the internal swapping does not happen.
Trying to store anything that is not a RFC 4122 variant is an error. Trying to store anything that is a RFC 4122 variant but not a Type 1 to 6 is an error.
https://s.yimg.com/os/creatr-uploaded-images/2021-03/d3b0ca20-7d26-11eb-bfbd-3af2156b896dToday, the US Supreme Court ruled 6-2 in favor of Google in the company’s long-running legal battle against Oracle.Engadget
A Soviet television adaptation of The Lord of the Rings thought to have been lost to time was rediscovered and posted on YouTube last week, delighting Russian-language fans of JRR Tolkien. From a report: The 1991 made-for-TV film, Khraniteli, based on Tolkien’s The Fellowship of the Ring, is the only adaptation of his Lord of the Rings trilogy believed to have been made in the Soviet Union. Aired 10 years before the release of the first instalment of Peter Jackson’s movie trilogy, the low-budget film appears ripped from another age: the costumes and sets are rudimentary, the special effects are ludicrous, and many of the scenes look more like a theatre production than a feature-length film. The score, composed by Andrei Romanov of the rock band Akvarium, also lends a distinctly Soviet ambience to the production, which was reportedly aired just once on television before disappearing into the archives of Leningrad Television. Few knew about its existence until Leningrad Television’s successor, 5TV, abruptly posted the film to YouTube last week [part one | part two], where it has gained almost 400,000 views within several days.
The Council of Elrond discusses the fate of the One Ring.
Gollum hams it up in a cave.
Unlike the Peter Jackson film, the mysterious Tom Bombadil plays a pivotal role in this interpretation.
Frodo and Aragorn are ready for battle.
Gandalf battles his enemies. It’s impossible to capture how wild the battle scenes are with a still image; you’ll have to watch for yourself.
Boromir monologues into the camera.
A narrator smokes a pipe as he frames the story.
After 30 years, a TV adaptation of J.R.R. Tolkien’s The Lord of the Rings long thought lost has resurfaced. The 1991 Soviet television adaptation has been uploaded to YouTube, in two one-hour videos.
The film focuses on the events of the first book in the trilogy, The Fellowship of the Ring, and features many elements that were excluded from the popular global theatrical release by director Peter Jackson, including an extended sequence featuring the character Tom Bombadil—one of the biggest omissions by the bigger-budget 2001 film far more of us have seen.
Originally broadcast on TV in 1991 (and then never aired again), the film was thought lost to time by those who had seen it. But as
in The Guardian, Leningrad Television successor Channel 5 uploaded the film to its YouTube page with little fanfare, surprising fans who had given up on seeing the production again. It is believed to be the only adaptation of these books produced in the Soviet Union.
For better or for worse, the primitive special effects and low budget are very apparent—moreso than in many other B movies of the time you may have seen. Grainy characters’ arms are cropped out in the middle of the frame as they are set against fuzzy fake backgrounds. And the film employs a visual language that is altogether alien to modern cinema, with sets and costumes that look more at home in a low-budget theatrical production and characters who gaze into the camera directly when they speak with eerie commitment.
In other words, an Andrei Tarkovsky masterwork it is not. But the nostalgia is strong, in particular thanks to the soundtrack by Andrei Romanov, who performed with the popular Russian rock group Akvarium.
Titled Khraniteli (“Keepers”), the film is believed to be based on a Russian-language translation of Tolkien’s work by Vladimir Muravyov and Andrey Kistyakovsky, and it is of course in Russian. But if you don’t speak Russian, fret not: YouTube’s autogenerated English closed captioning is adequate enough to give you the gist of what’s happening.
Christopher Schwarz is well-known in the woodworking industry, from his articles at Popular Woodworking, to his Lost Art Press publishing company.
You might have seen some of his books before, such as his book on workbench design, theory, construction, and use, which is available via Amazon.
I wrote about some of Schwarz’ “Anarchist” books before, and they’re quite good. They’re unlike any other woodworking or how-to books I’ve ever read before, and are somehow as conversational as they are informative.
Schwarz came out with a new book last year – The Anarchist’s Workbench. It seems I missed this news, as I only first learned of this book last night.
He describes The Anarchists’ Workbench as:
a detailed plan for a simple workbench that can be built using construction lumber and basic woodworking tools. But it’s also the story of Christopher Schwarz’s 20-year journey researching, building and refining historical workbenches until there was nothing left to improve.
There are two versions of The Anarchist’s Workbench – a hardcover copy, priced at $27, and a digital copy that Lost Art Press is giving away for free. That’s right, free, as in $0, and without any DRM or catches of any kind.
Why would Schwarz give this book away for free? In a blog post, he says that 1) he could afford to, 2) some people might hesitantly believe this new book too closely resembles his previous books, and so the free copy can serve as a sort of preview for them, and lastly:
Finally, I want this information – my last book on benches – to be free and widely available to everyone today and in the future. By putting it out there for free, I hope people will be inspired to build a bench, even if it’s not the bench in this book.
I’ve purchased some of the other books published by Lost Art Press, by the same and different authors, and they are very well-made. Even with a free PDF copy, I might eventually buy a hard copy (once I’m done with my currently very long reading list), and I imagine others will to.
I’ve read through some parts of The Anarchist’s Workbench already, and it’s an enjoyable book.
In this book, Schwarz discusses the how and why behind his design for a woodworking workbench sourced from home center lumber, and he also shares details about the personal and woodworking journey that has brought him here.
What is always refreshing about Schwarz’s writings these days is that he isn’t shackled by popular opinion, or the need to stay within anyone else’s lines.
This is a good book, and if it’s not quite your style, keep it in mind. Personally, I’m leaning towards a woodworking workbench direction I never would have thought I’d go in, and so never say never. If you like what you read, consider buying a physical copy.
All of our books are printed in the United States on the best materials we can obtain. We manufacture all of our books to last at least a century. That means using expensive sewn bindings, fiber tape and thick hardbacks (when possible).
“This is gonna be a quick race, folks.” YouTuber Steve Wilkins and his young sidekicks Tyler and Dylan have been posting a series of videos in which he races toy cars on his treadmill. In this clip, they put 100 cars on the belt, then cranked up the speed, resulting in a chaotic start that quickly culls the field.
A Left leaning US Army General getting a paycheck from CNN:
A Republican United States Senator from South Carolina:
In 1994, there was an Assault Weapons Ban – the evidence indicates that there was really no change at all in crime, because the crooks are going to get a gun!
A Left leaning US Army General getting a paycheck from CNN:
A Republican United States Senator from South Carolina:
In 1994, there was an Assault Weapons Ban – the evidence indicates that there was really no change at all in crime, because the crooks are going to get a gun!
In my opinion, Eloquent is one of the most powerful features of Laravel. It is an API for interacting with your database, and it has a very nice and easy-to-remember syntax. For example:
$post->author->name;
Will give you the name of the post’s author.
This is an example of an Eloquent relationship. Relationships define how your models (tables) are connected. Although most are easy to understand, there are a few more complicated ones.
In this post, I’m going to show how every relationship works.
One to one (has one)
For this example, we have two models: a User and an Address. The User model holds information such as name, email address, and password, and the Address model holds information like country, state, city, etc.
A User has one Address
An Address belongs to a User
We may have this table structure:
users
id - integer
name - string
email - string
password - string
address
id - integer
country - string
city - string
user_id - integer
You can define these relationships like this:
// app/Models/User.php
public function address()
{
return $this->hasOne(Address::class);
}
Now you can access the user’s address using $user->address->city.
Note: for this to work, the Address model should have a user_id column.
Inverse (belongs to)
If you have an Address and want to find the corresponding User, then define this relationship:
// app/Models/Address.php
public function user()
{
return $this->belongsTo(User::class);
}
One to many (has many)
In this example, we have two models: a Post and a Category.
A Post belongs to a Category
A Category has many Posts
And we have this table structure:
categories
id - integer
name - string
posts
id - integer
title - string
category_id - integer
We can define this relationship like this:
// app/Models/Category.php
public function posts()
{
return $this->hasMany(Post::class);
}
And you can access all the posts like this:
foreach($category->posts as $post) {
//
}
Note: for this to work, the Post model should have a category_id column.
Many to one (belongs to)
In this example, we have two models: a Post and a Category.
A Post belongs to a Category
A Category has many Posts
And we have this table structure:
categories
id - integer
name - string
posts
id - integer
title - string
category_id - integer
We can define this relationship like this:
// app/Models/Post.php
public function category()
{
return $this->belongsTo(Category::class);
}
And you can access the Post‘s category like this:
$post->category->name;
Has many through
This relationship is a bit more difficult. In this example, we have three models: an Author, a Post, and a Language.
A Post belongs to an Author
An Author has many Posts
An Author “belongs” to a Language (speaks a language)
A Language has many Authors
For example, this is our table structure:
languages
id - integer
name - string
authors
id - integer
name - string
language_id - integer
posts
id - integer
title - string
author_id - integer
If we want to get all posts in a specific language, we can define this relationship:
// app/Models/Language.php
public function posts()
{
return $this->hasManyThrough(Post::class, User::class);
}
Now, we can get all posts using:
foreach($language->posts as $post) {
//
}
Inverse
If you now want to get the Language of a Post, you can just simply do this:
$post->user->language->name;
Many to many (belongs to many)
In this example, we have two models: a Product and a Tag.
A Product has many Tags
A Tag has many Products
And we may have this table structure:
products
id - integer
name - string
price - integer
tags
id - integer
name - string
product_tag
product_id - integer
tag_id - integer
Note: in the table structure, we have a third table, product_tag. This table connects products to tags.
Now we can define the relationships like this:
// app/Models/Product.php
public function tags()
{
return $this->belongsToMany(Tag::class);
}
// app/Models/Tag.php
public function products()
{
return $this->belongsToMany(Product::class);
}
Now we can get all tags/products using:
foreach($product->tags as $tag) {
//
}
foreach($tag->products as $product) {
//
}
In the next post, I’m going to show what polymorphic relationships are and how to use them. Thanks for reading!
