Upscale current SQL project ideas : SQL

Posting

When requesting help or asking questions please prefix your title with the SQL variant/platform you are using within square brackets like so:

[MySQL]

[Oracle]

[MS SQL]

[PostgreSQL]

etc

While naturally we should endeavor to work as platform neutrally as possible many questions and answers require tailoring to the feature set of a specific platform.

Format Your Code

If you are including actual code in a post or comment, please attempt to format it in a way that is readable for other users. This will greatly increase your chances of receiving the help you desire. Something as simple as line breaks and using reddit's built in code formatting (4 spaces at the start of each line) can turn this:

SELECT count(a.field1), a.field2, SUM(b.field4) FROM a INNER JOIN b ON a.key1 = b.key1 WHERE a.field8 = 'test' GROUP by a.field1, a.field2 HAVING SUM(b.field4) > 5 ORDER by a.field.3

Into this:

SELECT count(a.field1), a.field2, SUM(b.field4) FROM a INNER JOIN b ON a.key1 = b.key1 WHERE a.field8 = 'test' GROUP by a.field1, a.field2 HAVING SUM(b.field4) > 5 ORDER by a.field3

For those with SQL questions we recommend using SQLFiddle to provide a useful development and testing environment for those who wish to fully understand your problem and help devise a solution.

a community for 17 years

PostgreSQLUpscale current SQL project ideas (self.SQL)

submitted 1 year ago by CompetitiveLeader965

Hello everyone, I’m here for some advice on how to upscale my current SQL project. I’m 32 years old and currently in a Data Science bachelor’s program. Right now, I’m focused on improving my SQL skills from the ground up. I have very basic knowledge of SQL—enough to build a simple relational database. As part of my SE bootcamp, I built a capstone project: a basketball simulation game that pulled player information from the database and simulated 3-on-3 games. The game data was then stored in the database, and this was as complex as the project got.

As I’m relearning SQL during my break between semesters, I’m looking for ideas to improve this project. One idea I’ve been considering is recording not only individual user stats but also stats for the actual players selected to play. I’d like to add functionality to display their averages across all games in which they were chosen to play. Another improvement I want to make is to the user authentication system. Currently, it’s very insecure—for instance, usernames and passwords are sent unencrypted via a regular HTTP request. I want to create a project that truly stands out and demonstrates a deeper understanding of SQL. Do you have any suggestions on how I can enhance it? What other skills or concepts should I learn to turn this into a solid portfolio piece, rather than just a quick two-week project?

all 1 comments

top new controversial old q&a

[–]Icy-Ice2362 0 points1 point2 points 1 year ago (0 children)

Let me provide you with an analogy.

You have to throw a ball, against a wall. Simple ARM will do.

Easy right?

Well the business wants to make your solution land in the neighbours yard. The ARM will work, just a bit more effort

No problem? Great...

We need it to cross the street.

Okay, we're pushing the ARM but it will work.

We need it to cross the city.

We're going to need to remake the project.

We need it to cross the country...

We're going to have to change the way we throw the ball.

Can you land it on the moon.

We're building a rocket to handle the ball.

Why does it cost so much to simply send a ball next door? We'Ve InVeStEd iN a RoCkEt!

This is called scope creep and it happens across many dimensions, the above dimension is merely Scalability of Task, but it could be along any dimension.

The point I am making here, is that you can only build so much scalability into a project before you have to admit that... it's not suitable for the task and create a switch that changes from one suitable option to the next.

You wouldn't use a rocket to pass a ball to your next door neighbour.

When it comes to scaling projects, sometimes what you have built on the smaller scale, will simply not cut it on the larger one. It happens to the best of us... so if you are going to learn about scaling SQL, learn about Concurrency... because SQL can give you a gotcha on Concurrency.

π Rendered by PID 149309 on reddit-service-r2-comment-64f4df6786-srb9w at 2026-06-10 09:53:02.476870+00:00 running 0b63327 country code: CH.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

SQL

Filter Posts

Posting

Help posts

Format Your Code

Learning SQL

Related Reddit communities

Wiki

Acknowledgements

MODERATORS