H2 vs PostgreSQL schema mismatch caused silent production enum failure

·1 views

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.

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)

Oracle AI Database 26ai Introduces Deep Data Security for Row and Column Access Control

Oracle AI Database 26ai has introduced a feature called Oracle Deep Data Security (Deep Sec), a database-enforced authorization framework that controls access at the row, column, and cell level. Unlike traditional application-layer security, Deep Sec enforces access policies directly within the database, regardless of whether the request originates from a human user, a reporting tool, or an AI agent. The system introduces three new building blocks: local end users (lightweight identities that own no schema), data roles (fine-grained privilege carriers that can sync with external identity providers like Microsoft Entra ID), and data grants (SQL-native policy objects defining read/write permissions). Local end users are created with a new CREATE END USER statement and tracked via a dedicated DBA_END_USERS dictionary view, but they cannot connect independently and must be authorized through data roles and grants. The feature is designed to complement existing Oracle tools like Label Security and Data Masking while offering a cleaner, more scalable approach to least-privilege access enforcement.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Responsibly Integrate AI Into US Building Permit Workflows

A structured pipeline for using AI in US building permit processes treats AI outputs as unverified drafts that require human classification, documentation, and licensed professional review before submission. The approach involves logging metadata for every AI-generated output, including the model used, prompt, data sources, and a named review owner, to maintain clear provenance. AI is considered appropriate for early-stage tasks such as massing studies, facade options, and site summaries, while code-critical elements like egress, structural loads, and energy compliance remain under licensed human oversight. Before a licensed architect or engineer signs off, any unverified AI-generated geometry must be removed or replaced with checked, authoritative information so building officials can distinguish controlled documents from exploratory references. The framework acknowledges that ongoing federal AI governance guidance and unresolved US Copyright Office questions around AI outputs make thorough documentation more reliable than asserting ownership over generated content.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Hardware Timestamping and PTP Eliminate Jitter in Distributed Systems

Software-based timestamps in distributed systems introduce variable delays ranging from microseconds to milliseconds due to interrupt handling, scheduler preemption, and NIC queues, making them unreliable for precision-critical applications. Hardware timestamping, by contrast, captures the exact moment a packet hits the network interface card, pushing timing uncertainty down to the nanosecond range. Systems such as high-frequency trading platforms, distributed databases, and PTP-synchronized networks depend on this accuracy to maintain correct event ordering and regulatory auditability. The IEEE 1588 Precision Time Protocol is specifically designed to leverage hardware timestamps and a hierarchical clock model to compensate for network-path delays. Tools like linuxptp, along with kernel interfaces such as ethtool and SIOCSHWTSTAMP, allow engineers to enable and validate hardware timestamping on commodity Linux systems.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds CLI tool to sequence Spotify playlists, learns hard lessons about API stability

A developer created 'setlisted', an open-source command-line tool that sequences Spotify playlists into structured sets with a warm-up, build, peak, and cooldown arc using only track metadata. The tool also generates discovery mixes without repetition and builds hour-targeted event sets to an exact duration. During development, the project hit a silent API breakage when Spotify renamed a field mid-response, leaving the old field populated with a boolean instead of its original object, causing logic errors that bypassed standard null and existence checks. This led the developer to adopt a principle of validating field types, not just presence, and building core functionality on durable metadata rather than rich fields that are more likely to be restricted. The project doubles as a case study in defensive API integration, with the author recommending diffing raw API responses when output goes subtly wrong without any errors thrown.

0 comments Read more at DEV Community