Skip to content

Align schema definitions and READMEs with actual Java code#31

Open
pmalirz wants to merge 1 commit into
mainfrom
fix/align-schema-and-docs-4587391659440173615
Open

Align schema definitions and READMEs with actual Java code#31
pmalirz wants to merge 1 commit into
mainfrom
fix/align-schema-and-docs-4587391659440173615

Conversation

@pmalirz

@pmalirz pmalirz commented Mar 19, 2026

Copy link
Copy Markdown
Owner

This commit aligns the database schema definitions (both the actual setup scripts and the documentation examples) with the underlying Java code.

Specifically, the Java API uses a long for expirationSeconds, but the SQL schema scripts and documentation used int (or INTEGER). These have been corrected to BIGINT (and NUMBER(19) for Oracle) to prevent potential truncation or mismatch errors at the JDBC boundary.

Additionally, DATETIME was changed to TIMESTAMP in H2 and Oracle scripts for better consistency across supported databases.

The API README was also synced with the actual Javadoc tags found in KeyLock.java, fixing the documentation-to-code drift.


PR created automatically by Jules for task 4587391659440173615 started by @pmalirz

- Updated H2, PostgreSQL, and Oracle create table scripts to use BIGINT (or NUMBER(19)) for EXPIRE_SEC to align with the Java API's `long expirationSeconds`.
- Updated H2 and Oracle scripts to use TIMESTAMP instead of DATETIME for consistency.
- Updated main README.md SQL example to use TIMESTAMP and BIGINT.
- Updated dlock-api/README.md to exactly match the Javadocs in KeyLock.java, including `{@value}` references and updated tags.

Co-authored-by: pmalirz <19637300+pmalirz@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant