Skip to content

[Bug]: Table 'bookingReference' can't use a non-unique index without a primary index #32

@waptik

Description

@waptik

So i came across some serious bug which i think it is. I was moving forward with my project when i noticed an error while querying an index field. I thought it was some code error on my part but i found no error after hours of searching.
So i updated my demo example and tried it there after updating to latest version.
At this location, https://github.com/waptik/test-deno-pentagon/blob/main/main.ts#L67, you can replace the value of meetingId with crypto.randomUUID() and you'll still get the error found in the screenshot.
If you remove .describe('index') from https://github.com/waptik/test-deno-pentagon/blob/main/db.ts#L80 and save the file, the code will run perfectly without errors.

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions