In this episode of Zero to CEO I speak to Web3 Infrastructure Builder James Bayly of subquery.network about the fundamentals of building a Web3 SaaS business. We delve into the topics of building a sustainable business in blockchain, and how driving community growth is critical to your success. We discuss the difference between token versus equity projects, Tokenomics, community growth strategies in web3, and how to market in this space, especially during a bear market. 

The SQL Subquery

Now that you’ve learned about SQL Joins, aggregate functionsand the group by keyword, it’s time we moved on to our final topic in our SQL tutorial series. Today you’ll be learning all about SQL Subqueries, how to use them and when you should use a SQL subquery.

So, what is a subquery?

First and foremost, let’s get the jargon out of the way. A subquery can also be referred to as a nested query. It’s just like having a nested if statement in your Java code. Essentially what you’re doing with a subquery is you are constructing a regular old query (select statement) which could be run all by itself if you wanted to, but instead of running it all by itself, you’re jamming it into another query (select statement) to give you more specific (filtered) results.

What’s very important to note here is that the SQL subquery can almost always be re-written as a join with a whereclause attached to it.

More info on this via http://howtoprogramwithjava.com/session49

The SQL Subquery

Now that you’ve learned about SQL Joins, aggregate functionsand the group by keyword, it’s time we moved on to our final topic in our SQL tutorial series. Today you’ll be learning all about SQL Subqueries, how to use them and when you should use a SQL subquery.

So, what is a subquery?

First and foremost, let’s get the jargon out of the way. A subquery can also be referred to as a nested query. It’s just like having a nested if statement in your Java code. Essentially what you’re doing with a subquery is you are constructing a regular old query (select statement) which could be run all by itself if you wanted to, but instead of running it all by itself, you’re jamming it into another query (select statement) to give you more specific (filtered) results.

What’s very important to note here is that the SQL subquery can almost always be re-written as a join with a whereclause attached to it.

More info on this via http://howtoprogramwithjava.com/session49

The SQL Subquery

Now that you’ve learned about SQL Joins, aggregate functionsand the group by keyword, it’s time we moved on to our final topic in our SQL tutorial series. Today you’ll be learning all about SQL Subqueries, how to use them and when you should use a SQL subquery.

So, what is a subquery?

First and foremost, let’s get the jargon out of the way. A subquery can also be referred to as a nested query. It’s just like having a nested if statement in your Java code. Essentially what you’re doing with a subquery is you are constructing a regular old query (select statement) which could be run all by itself if you wanted to, but instead of running it all by itself, you’re jamming it into another query (select statement) to give you more specific (filtered) results.

What’s very important to note here is that the SQL subquery can almost always be re-written as a join with a whereclause attached to it.

More info on this via http://howtoprogramwithjava.com/session49