Redis driver: enforce unique ID constraint on create

[Copilot]

Redis driver was silently overwriting records on duplicate IDs instead of throwing. TCK test "should throw error on duplicate ID" failed.

Changes

RedisDriver.create() now uses SET ... NX to atomically check-and-set:

// Before: unconditional write
await this.client.set(key, JSON.stringify(doc));

// After: conditional write with duplicate detection
const result = await this.client.set(key, JSON.stringify(doc), { NX: true });
if (!result) {
    throw new Error(`Record with ID ${id} already exists in ${objectName}`);
}

Aligns behavior with other drivers (MongoDB, SQL) which reject duplicate primary keys.

Original prompt

引用: https://github.com/objectstack-ai/objectql/actions/runs/21579177618/job/62172785839#step:9:1

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectql	Ready	Preview, Comment	Feb 2, 2026 6:35am

[Copilot]

Pull request overview

Enforces a uniqueness constraint for RedisDriver.create() by preventing silent overwrites when a record with the same ID already exists, aligning Redis driver behavior with other drivers and fixing the failing TCK case.

Changes:

• Replace unconditional SET with conditional SET ... NX to avoid overwriting existing records
• Throw an error when the key already exists (duplicate ID)

[Copilot]

SET with NX typically returns 'OK' on success and null on failure (duplicate). Using if (!result) works, but it’s clearer/safer to check explicitly for the expected failure value (e.g., result === null) or success value (e.g., result !== 'OK') to avoid any ambiguity if return types change across Redis clients.

Suggested change

	if (!result) {
	if (result === null) {

[Copilot]

Throwing a plain Error makes it harder for callers (and cross-driver behavior) to reliably detect a duplicate-ID condition. If the project has a standard duplicate/constraint error type or error code used by other drivers, throw that here (or wrap with a distinct name/code) so consumers can handle duplicates consistently without parsing the message.