I am one of the developers on a very small team and have just found the following query
I would love to hear your ideas for what you think was being attempted here!
SELECT ... FROM client WHERE CAST(ABS(SIN(clientId)) AS BIT) = 0
what's your take on SQL style guides? Especially this one
Modern SQL Style Guide
https://gist.github.com/mattmc3/38a85e6a4ca1093816c08d4815fbebfb
Modern SQL Style Guide. GitHub Gist: instantly share code, notes, and snippets.
Gizmo - Security & Performance
https://kerkour.com/sqlite-for-servers
My workflow for writing SQL(ite) queries (2024 edition)
My workflow for writing SQL(ite) queries (2024 edition) · Jamie Tanna | Software Engineer
https://www.jvt.me/posts/2024/06/07/sql-workflow/
Writing about my recent workflow for writing, executing, and sharing SQL queries with others.
POSETTE: An Event for Postgres 2024 | 3rd annual virtual event organized by the Postgres team at Microsoft | 48 Hours of Virtual Presentations and Meetings Starting Tue, June 11 @ 3:00 PM UTC
POSETTE: An Event for Postgres 2024
https://www.citusdata.com/posette/2024/
Join us at POSETTE: An Event for Postgres (formerly Citus Con), a virtual and free developer event happening on Jun 11-13, 2024. Come learn what you can do with the world’s most advanced open source relational database—from the nerdy to the sublime. Organized by the Postgres team at Microsoft.
Hello! Let me first clarify, this is for a personal project, based on an idea I always use to learn all kinds of things: personal finance tracking.
The DB model I typically use looks something like this:
Initially, I made the decision to separate incomes, expenses and transfers into separate tables, which makes sense to me, according to the way I learned DB normalization.
But I was wondering if there is any benefit in somehow mixing the expense and income tables (since they are almost identical, and any code around these is always almost identical), or even all 3 (expense, income and transfer). Maybe it is more convenient to have the data modeled like this this for an API, but for BI or analytics, a different format would be more convenient? How would such format look like? Or maybe this would be better for BI and analytics, but for an API it's more convenient to have something different?
A while ago at a previous job, an experienced software architect once suggested, for a transactional system, to separate the transactional DB from a historical DB, and continuously migrate the data differences through ETL's. I have always thought that idea is pretty interesting, so I wonder if it makes sense to try in my little personal project.
If it was you, how would you model personal finance tracking? Is there something you think I may be missing, or that I should look into for DB modeling?
(Note: I intentionally do not track loans / investments, or at least I have not tried to integrate it for the sake of simplicity, and I have no interest in trying YET.)
Is there a programming language specifically designed for interacting with SQL databases that avoids the need for Object-Relational Mappers (ORMs) to solve impedance mismatch from the start?
If such a language exists, would it be a viable alternative to PHP or Go for a web backend project?
SQL for the Weary
SQL for the Weary
https://gvwilson.github.io/sql-tutorial/
Learning SQL
I’ve started to take an intro SQL class but I want to find more places to practice. Do any of you have recommendations for sites that I can use to practice creating queries based on pieces of information someone is looking for?
Any other advice to give to a brand new SQL learner?
Thanks in advance for any guidance.
Edit: Thanks a ton for the responses, I really appreciate it. I’ve bookmarked these pages and started to go through these sites.
Troublesome words in SQL
https://modern-sql.com/reserved-words-empirical-list
These words cause problems as table or column name