**SHOP TUTORIAL PRODUCTS BELOW**
This tutorial takes you through the step-by-step process of making statement earrings that don't dangle so far from your ear! I love a good post, and I'm going to show you how to turn your favorite bead and shell elements into a WOW factor with wire, earring backs and two-part epoxy glue! This also works well for clip-on earrings style and folks without pierced ears. You can purchase jewelry making supplies or find out more at ChristineWhiteStyle.com
-22 gauge craft wire: https://christinewhitestyle.com/collections/wire-and-stringing-materials/products/non-tarnish-22-gauge-wire
-flat beads: https://christinewhitestyle.com/products/flat-wood-beads-4-pack
-glue-on posts: https://christinewhitestyle.com/products/glue-on-omega-post-backs
-two-part epoxy: https://christinewhitestyle.com/collections/adhesives/products/bead-fix-two-part-epoxy
-3 Piece Tool Kit: https://christinewhitestyle.com/collections/tools/products/3-piece-tool-set
Denise Winant thank you so much for watching! This video was filmed a short while ago, but I am working closely with my production company to ensure tight, slow closeups on all new videos. Making sure that these tutorials are easy to follow is my number one priority for all of you. Happy beading! -Christine 😊🌸
This article has been motivated by a response I gave to a problem raised on an Oracle developer forum. Our requirement is to produce a report that details customer spending for each month of the year. Our database only records actual spend, so for any given month, data for dormant or idle customers will have to be generated.
First, well create a mock CUSTOMER_ORDERS table with sparse data to represent customer spending. To keep the example simple, well denormalise the customer name onto the orders table.
a sparse report.
With our customer orders data as sparse as it is, a monthly report for purchases by customer would look as follows.
adding the missing months.
We can see from the data that we are missing most months of the year for our two customers. Remember that our requirement is to show a report for every month in 2004 for every customer. First we will build a "time dimension" set (using subquery factoring) and outer join it to our orders table.
We can see that this hasnt quite worked. We have the zero sums and the year-months, but we are missing customer names. This is because we outer joined to CUSTOMER_ORDERS on the year-months, so any customer columns would show as NULL for deficient rows. Until PARTITION OUTER JOIN appeared in Oracle 10g, we couldnt "invent" data easily , though the next section shows that it is possible in prior versions.
data-densification without partition outer join.