SQL is widely known for data querying and manipulation but systems do grow; data becomes larger; processes become repetitive and operations become sensitive. SQL has some features which enables it to be considered a fully fledged programming language. Some of the features which I discuss in this article are procedures, functions and transactions. Each of these concepts serve distinct purposes. Sto
Hi 👋, In this post we shall explore Bedrock's structured KB with this architecture: Upload CSVs to S3 > SNS Queue > Crawl data with Glue > Query with Redshift > Bedrock KB > Query with LLM. Let's do some of this with code. Let's get started. Clone the repo and switch to the project directory. git clone [email protected]:networkandcode/networkandcode.github.io.git cd structured-kb-demo/ Do a uv sync
There's a dangerous assumption most developers bring into Compact: "It's a privacy-first chain. My data is private unless I explicitly expose it." This is backwards. And it's where the serious mistakes happen. Compact doesn't give you automatic privacy. It gives you a hard boundary between two worlds, and a compiler that enforces it. World Where Who sees it Public On-chain, every network no
## INTRODUCTION Every blockchain application that handles value needs to answer the same question: how do you track who owns what? There are two dominant approaches, and choosing between them shapes your entire contract architecture. Contract-state accounting behaves like a bank ledger. A single smart contract holds a balance map, and transactions update entries in place. The UTXO model behaves li
Subqueries vs. CTEs in SQL: A Practical Guide to Writing Cleaner, Smarter Queries Whether you're just getting comfortable with SQL or leveling up your data skills, two tools will come up again and again when working with complex queries: subqueries and Common Table Expressions (CTEs). They solve similar problems — breaking a complex query into manageable pieces — but they do it in different ways
In a previous post, I explored Codd's connection trap in PostgreSQL and MongoDB — the classic pitfall where joining two independent many-to-many relationships through a shared attribute produces spurious combinations that look like facts but aren't. The example followed Codd's 1970 suppliers–parts–projects model: we know which suppliers supply which parts, and which projects use which parts, but j
Automating Hermitage to see how transactions differ in MySQL and MariaDB
Barman – Backup and Recovery Manager for PostgreSQL