fix(core): inline TrackRow SELECT in postgres list/get methods

[InstaZDLL]

Summary

Latent build break in PostgresTrackRepository (introduced in #186): sqlx 0.9's query_as takes impl SqlSafeStr, which only accepts a 'static literal. The previous version stored the shared projection in const SELECT_TRACK_ROW: &str and composed it via format!() at runtime — the resulting String failed to coerce when waveflow-server consumed waveflow-core with features = ["postgres"].

The desktop workspace check (cargo check --workspace --all-targets) didn't catch this because it doesn't activate the postgres Cargo feature on waveflow-core — that code path is only compiled when waveflow-server's git dep pulls it in.

Fix

Inline the full NULL-cast projection at each call site in list_for_library and get_for_library. insert_for_library, update_for_library, and delete_for_library already used literal strings (their INSERT/UPDATE/DELETE-specific shapes are method-local anyway) — no change needed.

Duplication is bounded; a future schema change would have touched each branch the same way anyway.

Follow-up

Worth adding cargo check --features postgres --all-targets (or --all-features) to the workspace check loop / CI so this feature-gated path gets compiled outside of waveflow-server's build.

Test plan

• cargo check --manifest-path src-tauri/crates/core/Cargo.toml --features postgres --all-targets
• cargo clippy --manifest-path src-tauri/crates/core/Cargo.toml --features postgres --all-targets -- -D warnings
• cargo test --workspace (45 passed, unchanged)

Summary by CodeRabbit

• Refactor
  • Optimisation interne du traitement des requêtes de base de données pour améliorer la stabilité et la compatibilité.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f9005178-a6a3-4446-b6bd-5c4430b84734

📥 Commits

Reviewing files that changed from the base of the PR and between 101aff5 and afebc83.

📒 Files selected for processing (1)

• src-tauri/crates/core/src/repository/postgres/track.rs

---

📝 Walkthrough

Aperçu

Le repository PostgreSQL pour les pistes inligne les projections SQL dans les méthodes list_for_library et get_for_library au lieu d'utiliser une constante partagée, pour se conformer à la contrainte 'static de sqlx 0.9.

Modifications

Migration vers projections SQL inlinées

Couche / Fichier(s)	Résumé
Inlining des projections SELECT src-tauri/crates/core/src/repository/postgres/track.rs	La constante SELECT_TRACK_ROW est remplacée par des projections inlinées dans les deux méthodes. Un commentaire explique que sqlx 0.9 requiert des littéraux 'static, rendant format!() non conforme. Les chaînes d'ownership et les filtres library_id sont préservés dans list_for_library et get_for_library.

Effort d'examen estimé

🎯 3 (Modéré) | ⏱️ ~20 minutes

PRs potentiellement liées

• InstaZDLL/WaveFlow#186: Mêmes ajustements de projections SQL inlinées sur le fichier track.rs.

Poème

📜 Les constantes SQL se transforment en requêtes inline,
sqlx 0.9 impose ses règles 'static si fines,
Ownership chaînes intactes, filtres préservés,
Pas de comportement nouveau, juste du code raffiné. 🎯

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	Le titre décrit précisément le changement principal : l'inlining des SELECT TrackRow dans les méthodes postgres list/get. Il suit le format Conventional Commits.
Description check	✅ Passed	La description couvre complètement le problème (sqlx 0.9 query_as avec 'static literal), la solution (inlining), les tests effectués et même recommande un suivi CI.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/postgres-track-query-as-literal

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}