Skip to content

Add build targets for Postgres and SQLite#112

Merged
leynos merged 1 commit intomainfrom
codex/make---features-postgres-disable-sqlite
Jun 12, 2025
Merged

Add build targets for Postgres and SQLite#112
leynos merged 1 commit intomainfrom
codex/make---features-postgres-disable-sqlite

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 12, 2025

Summary

  • add Makefile targets for debug and release builds of each backend

Testing

  • cargo clippy -- -D warnings
  • cargo test

https://chatgpt.com/codex/tasks/task_e_684ab6ef18e0832283f4c4ddd85e3c11

Summary by Sourcery

Add Makefile targets to build the mxd binary with SQLite and Postgres backends in both debug and release modes.

New Features:

  • Introduce 'sqlite' and 'sqlite-release' targets for building with the SQLite feature.
  • Introduce 'postgres' and 'postgres-release' targets for building with the Postgres feature using an isolated target directory.

Summary by CodeRabbit

  • Chores
    • Added new build options for creating binaries with either SQLite or Postgres support, available for both debug and release modes.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 12, 2025

Reviewer's Guide

Adds debug and release build targets for SQLite and Postgres in the Makefile by defining PHONY entries, top-level target aliases, and specific cargo build rules with proper features and target directories.

Sequence Diagram for 'make postgres-release' Target Interaction

sequenceDiagram
    actor Developer
    participant Make
    participant Cargo

    Developer->>Make: "make postgres-release"
    Make->>Make: "Resolve 'postgres-release' (depends on 'target/postgres/release/mxd')"
    Make->>Cargo: "Execute rule for 'target/postgres/release/mxd':\ncargo build --release --bin mxd\n--no-default-features --features postgres\n--target-dir target/postgres"
    Cargo->>Cargo: "Compile project (release, postgres feature)"
    Cargo-->>Make: "Build Succeeded / Failed"
    Make-->>Developer: "Display build output"
Loading

Flow Diagram of New Makefile Build Target Commands

graph TD
    A[Developer executes 'make <target>'] --> B{Select Target};
    B -- "sqlite" --> C["Rule: target/debug/mxd <br/>Cmd: cargo build --bin mxd <br/>--features sqlite"];
    C --> D[SQLite Debug Build];
    B -- "postgres" --> E["Rule: target/postgres/debug/mxd <br/>Cmd: cargo build --bin mxd <br/>--no-default-features --features postgres <br/>--target-dir target/postgres"];
    E --> F[Postgres Debug Build];
    B -- "sqlite-release" --> G["Rule: target/release/mxd <br/>Cmd: cargo build --release --bin mxd <br/>--features sqlite"];
    G --> H[SQLite Release Build];
    B -- "postgres-release" --> I["Rule: target/postgres/release/mxd <br/>Cmd: cargo build --release --bin mxd <br/>--no-default-features --features postgres <br/>--target-dir target/postgres"];
    I --> J[Postgres Release Build];
Loading

File-Level Changes

Change Details Files
Expanded PHONY targets to include new build aliases
  • Added 'sqlite', 'postgres', 'sqlite-release', 'postgres-release' to .PHONY
Makefile
Defined top-level Makefile targets for each backend and build mode
  • Created 'sqlite' and 'postgres' targets pointing to debug binaries
  • Created 'sqlite-release' and 'postgres-release' targets pointing to release binaries
Makefile
Implemented build rules invoking cargo with appropriate flags
  • Debug build for SQLite with --features sqlite
  • Debug build for Postgres with --no-default-features, --features postgres, and custom target-dir
  • Release build for SQLite with --release and --features sqlite
  • Release build for Postgres with --release, --no-default-features, --features postgres, and custom target-dir
Makefile

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 12, 2025

Walkthrough

The Makefile has been updated to introduce four new phony targets: sqlite, postgres, sqlite-release, and postgres-release. These targets enable building the mxd binary with either SQLite or PostgreSQL features in both debug and release configurations, directing outputs to appropriate directories.

Changes

File Change Summary
Makefile Added phony targets for sqlite, postgres, sqlite-release, and postgres-release with specific build commands.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Makefile
    participant Cargo

    Developer->>Makefile: make sqlite / make sqlite-release
    Makefile->>Cargo: build mxd with sqlite feature (debug/release)

    Developer->>Makefile: make postgres / make postgres-release
    Makefile->>Cargo: build mxd with postgres feature (debug/release, no default features, output to target/postgres)
Loading

Possibly related PRs

Suggested reviewers

  • codescene-delta-analysis

Poem

A Makefile hop, a feature leap,
With targets new for builds to keep.
SQLite or Postgres, debug or release,
Compile with ease, let worries cease.
The rabbit cheers, the builds are neat—
Now every flavour’s at your feet!
🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Want more control? Customize Code Health rules or catch issues early with our IDE extension and CLI tool.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 653d07d and 70dd187.

📒 Files selected for processing (1)
  • Makefile (1 hunks)
🧰 Additional context used
🪛 checkmake (0.2.2)
Makefile

[warning] 1-1: Missing required phony target "all"

(minphony)


[warning] 1-1: Missing required phony target "clean"

(minphony)


[warning] 1-1: Missing required phony target "test"

(minphony)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build-test (postgres)
  • GitHub Check: coverage
  • GitHub Check: build-test (sqlite)
🔇 Additional comments (5)
Makefile (5)

6-9: Define clear, backend-specific aliases

The new phony targets (sqlite, postgres, sqlite-release, postgres-release) cleanly map to their build prerequisites and improve discoverability of each backend build.


11-12: Build debug binary with SQLite feature

The target/debug/mxd rule correctly invokes cargo build --features sqlite. Ensure the recipe line uses a leading tab for compatibility.


14-15: Build debug binary with PostgreSQL feature

The target/postgres/debug/mxd rule appropriately disables default features and isolates artifacts under target/postgres.


17-18: Build release binary with SQLite feature

The target/release/mxd rule mirrors the debug variant in release mode using the sqlite feature—consistent and clear.


20-21: Build release binary with PostgreSQL feature

The target/postgres/release/mxd rule cleanly parallels the debug target, keeping PostgreSQL artifacts separate for parallel builds.

Comment thread Makefile
Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos leynos merged commit b99eca4 into main Jun 12, 2025
3 of 5 checks passed
@leynos leynos deleted the codex/make---features-postgres-disable-sqlite branch June 12, 2025 11:53
This was referenced Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant