Developer builds CoffeeQL, a Rust-based universal query language for four databases

·1 views

A developer has released CoffeeQL v0.3.1, an open-source query language written in Rust that provides a single unified syntax for querying PostgreSQL, MongoDB, MySQL, and Redis. The project was motivated by the cognitive overhead of constantly switching between four different query syntaxes in a typical backend engineering workflow. CoffeeQL uses a custom readable syntax — such as users[].where(id = 1).give(name, email) — and internally translates queries to the appropriate database format. The library is available on both npm via WebAssembly and PyPI via Python bindings, with 265 tests currently passing. The upcoming v0.4.0 release is planned to add actual query execution support, with full CRUD operations across all supported databases.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

CS Student Documents Shift from Python to Go and Rust Systems Programming

A first-year Software Engineering student has announced a transition from Python web development to systems programming, focusing on Go and Rust. The student has set up a development environment using Windows 10 with WSL 2 (Debian), VS Code, and Docker, and has already compiled a first Go program. Over the next year, the student plans to master low-level concepts such as memory management, pointers, and asynchronous I/O, while building multiple projects. The longer-term goal is to develop security agents for the Linux kernel using Rust by the third year of study. The student intends to document the entire learning journey on Dev.to and share code publicly on GitHub.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Uses Coding Metaphors to Reflect on Revisiting a 12-Year-Old Heartbreak

A software developer recently discovered an old personal archive on a hard drive containing remnants of a 12-year-old relationship. Using programming terminology, they described the experience as 'recompiling legacy code' that caused unexpected emotional disruption. The developer documented the reflective process as a technical investigation, complete with metaphors like firewall rules and background processes to represent unresolved feelings. The full write-up, framed as a code repository post-mortem, has been made publicly available on GitHub and a personal website in French.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

H2 vs PostgreSQL schema mismatch caused silent production enum failure

A batch job in production began failing with an invalid enum error after a migration that had passed cleanly in an H2-based test environment. The root cause was a divergence between test and production migration scripts: H2 stored the status field as a plain VARCHAR, while PostgreSQL enforced it as a native three-value enum — ACTIVE, INACTIVE, and ARCHIVED. A legacy status value, LEGACY_HIDDEN, was silently accepted by H2 but correctly rejected by PostgreSQL's stricter type enforcement. The team switched to Testcontainers running the real PostgreSQL migration script, and the same failure surfaced immediately in a local test run. The incident highlights that in-memory test databases like H2 can miss entire classes of schema-level errors when production uses database-native constraints or enum types.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Step-by-Step Guide: Connecting Microsoft Intune with Apple Business Manager for iPhone Enrollment

IT administrators can use Automated Device Enrollment (ADE) to automatically enroll corporate iPhones into Microsoft Intune during initial device setup, eliminating the need for manual staging. The process requires completing prerequisites in sequence, including setting the MDM authority, obtaining an APNs certificate, and creating an enrollment program token that links Apple Business Manager (ABM) with Intune. Devices must be associated with ABM either through an Apple-authorized reseller at the time of purchase or manually via Apple Configurator, with reseller-purchased devices receiving stronger management controls and no provisional release period. Once devices are assigned to the MDM server in ABM and an enrollment profile is created and assigned in Intune, iPhones can be handed directly to users straight out of the box. ADE also enables Supervised mode, which grants administrators broader control over device settings, app installation restrictions, and feature management compared to manual enrollment methods.

0 comments Read more at DEV Community