duplicates

TWO MANY JANEWAYS? That's the conundrum at the heart of season two standout "Deadlock," and joining Bryan this week is Captain Janeway superfan Marina Kravchuk from Daily Star Trek News to talk all about. There's a lot of technobabble that only makes sense because of the years of world building going on since the TNG days, but there's also a lot of Voyager-specific tropes deployed in an episode that finds Voyager being duplicated because of a rift in subspace. And there are Vidians thrown in for good measure! Is it a Trek, Marry, or Kill?

Check out all our Trek Marry Kill standings at TrekMarryKillPod.com. You can follow our guest on social media @drakkorex on most platforms. 

We need to be serving others, believe that we can serve them in the way that they need, and believe that God will provide the resources we need to do the serving.

Main Scripture: Luke 9:10-11, Luke 9:12-15, Luke 9:16-17
Bible Translation: CSB

Welcome to GodSquad Church, a church for gamers!

If you made a decision to follow Christ, let us know by filling out this quick form so that we can reach out to you with some resources.
https://www.godsquadchurch.com/next-level

To support this ministry and help us continue to help gamers win together, click here: https://www.godsquadchurch.com/give

You can also listen to an audio version of this message on any of our podcast platforms! Spotify, Google Podcasts, Apple Podcasts, or Transistor

——————

Get Connected!
Discord: https://discord.gg/ztNgwBs
Twitch (GodSquad Church): https://www.twitch.tv/godsquadchurch
Twitter: https://www.twitter.com/GodSquadChurch
Facebook: https://www.facebook.com/gaming/GodSquadGaming
Instagram: https://www.instagram.com/godsquad_church
TikTok: https://www.tiktok.com/@godsquadchurch

More Info at: https://www.godsquadchurch.com

Why is it that when we decide to undertake something that’s going to make a difference in our lives, we still try to cut corners?

When I decided to go back to school in pursuit of a PhD, my mindset was initially to make the supplies and things I already had work for my school venture. But when I’ve needed something, I’ve found it’s just better to go ahead and get it. Some of these supplies help me move forward faster, be more productive and/or just be able to get my assignments and reading done in different places.

Do you have the supplies or tools you need where you need them? It makes all the difference. Listen to my story about scissors to find out why.

Here are some of my favorite supplies mentioned in today’s podcast:

• Fiskars scissors
• Shokz Wireless Open-Ear Bluetooth Headset
• Organize 365® 2.0 Highlighters
• Organize 365® 2.0 Productivity Tabs
• Organize 365® Slash Pockets
• Jergens Cherry Almond Lotion

Don’t live in frustration over not having what you need where you need it. The time and sanity savings will offset the investment.

EPISODE RESOURCES:

• Follow my journey on Instagram - Check out the PhD Highlight Button

Did you enjoy this episode? Please leave a rating and review in your favorite podcast app. Share this episode with a friend and be sure to tag Organize 365® when you share on social media!

Episode 57 Summary

This week, we’ll be discussing some more great modern horror. We’ll take a look at “The Lighthouse,” “Crawl”, “Us”, “Eternal Code,” and “One Cut of the Dead,” all from 2019.  Let’s get to it!

There’s a lot to talk about, so. Here. We. Go.

Current Classic: “The Lighthouse” (2019)
Amazon Link: https://amzn.to/2TaXgmM

Current Classic: “Crawl” (2019)
Amazon Link: https://amzn.to/37R5ODl

Current Classic: “Us” (2019)
Amazon Link: https://amzn.to/305x6mQ

Current Classic: “One Cut of the Dead” (2019)
Amazon Link: https://amzn.to/2QI72ep

Bonus Film: “Eternal Code” (2019)
Amazon Link: https://amzn.to/35HlgR1

Closing

And that’s our show. Thanks for joining us. Stop in during the week at our website for news and horror updates, to comment on this podcast, or to contact us. 

Get ready for next week, where we’ll be discussing some more great modern horror. We’ll briefly head back to the usual format take a look at “Dead Man’s Eyes” (1944), “The Gorgon” (1964), The remake of “Pet Sematary” from 2019, and the International “Kairo/Pulse” from 2001. The following week, we’ll meet up with four more modern films, all starring Annabelle and Chucky.  

Email: horrorguysmail@gmail.com
YouTube: https://www.youtube.com/channel/UCvIqIjVoNO0u78BykYKOMQQ
Facebook: https://www.facebook.com/horrorguyspodcast
Twitter: http://twitter.com/HorrorBulletin
Also http://twitter.com/BrianSchell   and http://twitter.com/EightyCoin
The web: http://www.horrorguys.com
Patreon: http://patreon.com/horrorguys
Buy us a coffee at http://Buymeacoffee.com/horrorguys

I’m Kevin. And I’m Brian. We’ll see you next time!
Theme Music by Kevin MacLeod of Incompetech.com

Brothers John and Will Wiesenfeld improve clones.

patreon.com/2PointOhPodcast

www.2PointOhPodcast.com

Podcast Twitter: @2PointOhPodcast

personal twitter/instagram:

Will: @BATHSmusic

John: @sweaterstripes

Theme: Will

Art: John

Course: Oblivion.  

Things are looking up for the Voyager crew at the beginning of the fifth-season episode "Course: Oblivion," from the wedding of Tom Paris and B'Elanna Torres to an enhanced warp drive. But that all changes when the ship and crew begin losing their molecular cohesion, only to discover that they are, in fact, merely biomimetic duplicates of the real Voyager ship and crew, created a year before when Voyager landed on the aptly named "Demon Planet."  

In this episode of To The Journey, hosts Zachary Fruhling and Suzanne Williamson (or perhaps their biomimetic duplicates; you be the judge!) discuss the merits of "Course: Oblivion." From the minutiae of the wedding of Fake-Tom and Fake-B'Elanna to the existential burdens of being a biomimetic duplicate, Zachary and Suzanne wrestle with  whether "Course: Oblivion" is as riveting as they recall and whether "Course: Oblivion" is really just one big metaphor for our finite human lives.  

Chapters 
Intro (00:00:00) 
Distinguished Melting Neelix (00:03:27) 
What about Harry Kim? (00:07:28) 
Warp Cores Are Like Cats (00:10:13) 
Who Is Ensign Harper?! (00:12:21) 
This Episode Is a Metaphor for Life (00:18:02) 
Goo People and an Enhanced Warp Drive (00:20:54) 
Tom with a Tommy Gun (00:25:07) 
Not as Riveting as We Remember (00:30:14) 
Goo Gone (00:34:40) 
Closing (00:37:49)  

Hosts 
Zachary Fruhling and Suzanne Williamson  

Production 
Suzanne Williamson (Editor) Zachary Fruhling (Producer) C Bryan Jones (Executive Producer) Matthew Rushing (Executive Producer) Ken Tripp (Executive Producer) Bruce Lish (Associate Producer) Joo Kim (Associate Producer) Richard Marquez (Associate Producer) Patrick Carlin (Associate Producer) Norman C. Lao (Associate Producer) Richard Marquez (Production Manager) Brandon-Shea Mutala (Patreon Manager)

How to Fix Duplicate Data from Hibernate Queries

This problem was the bane of my existence when I first started using Hibernate because I had no idea where the problem was coming from.

If you’re executing a query and finding that you have a bunch of duplicate records and haven’t a clue why, then you’re in the right place.

You see the problem is typically caused by having left joins (or optional joins) in your objects. When you have a base object, like say User and it joins to another table/object in an optional One-to-Many or optional Many-to-Many format, then you may get duplicates.

Consider this scenario… A User objects joins to the LoginHistory object, which keeps track of all the times a particularUser has logged into the system. And let’s say our user has logged in many times. You’ll have a situation where you have many records in the LoginHistory table.

So what happens when you run a query that joins to the LoginHistory table? Well it will return as many rows as there are entries for that User in the LoginHistory table.

So because of this, Hibernate doesn’t massage the data for you, it just returns exactly what it got from the database. The ball is in your court to tell Hibernate what to do with records it has retrieved.

There are two solutions to this problem:

1. Declare your joining object as a Set
2. Make use of Distinct Root Entity Results Transformer

Click Here to Keep Reading

How to Fix Duplicate Data from Hibernate Queries

This problem was the bane of my existence when I first started using Hibernate because I had no idea where the problem was coming from.

If you’re executing a query and finding that you have a bunch of duplicate records and haven’t a clue why, then you’re in the right place.

You see the problem is typically caused by having left joins (or optional joins) in your objects. When you have a base object, like say User and it joins to another table/object in an optional One-to-Many or optional Many-to-Many format, then you may get duplicates.

Consider this scenario… A User objects joins to the LoginHistory object, which keeps track of all the times a particularUser has logged into the system. And let’s say our user has logged in many times. You’ll have a situation where you have many records in the LoginHistory table.

So what happens when you run a query that joins to the LoginHistory table? Well it will return as many rows as there are entries for that User in the LoginHistory table.

So because of this, Hibernate doesn’t massage the data for you, it just returns exactly what it got from the database. The ball is in your court to tell Hibernate what to do with records it has retrieved.

There are two solutions to this problem:

1. Declare your joining object as a Set
2. Make use of Distinct Root Entity Results Transformer

Click Here to Keep Reading

How to Fix Duplicate Data from Hibernate Queries

This problem was the bane of my existence when I first started using Hibernate because I had no idea where the problem was coming from.

If you’re executing a query and finding that you have a bunch of duplicate records and haven’t a clue why, then you’re in the right place.

You see the problem is typically caused by having left joins (or optional joins) in your objects. When you have a base object, like say User and it joins to another table/object in an optional One-to-Many or optional Many-to-Many format, then you may get duplicates.

Consider this scenario… A User objects joins to the LoginHistory object, which keeps track of all the times a particularUser has logged into the system. And let’s say our user has logged in many times. You’ll have a situation where you have many records in the LoginHistory table.

So what happens when you run a query that joins to the LoginHistory table? Well it will return as many rows as there are entries for that User in the LoginHistory table.

So because of this, Hibernate doesn’t massage the data for you, it just returns exactly what it got from the database. The ball is in your court to tell Hibernate what to do with records it has retrieved.

There are two solutions to this problem:

1. Declare your joining object as a Set
2. Make use of Distinct Root Entity Results Transformer

Click Here to Keep Reading