Skip to content

Avoiding duplicates? #6

@coldino

Description

@coldino

Love the simplicity of this project in use, but I've come across an issue - how to avoid inserting duplicates?

It appears I would need to bypass the client and check each entry with the underlying connection before db.add. This just feels out of place with the simplicity of the rest of the interface, particularly as it would then need knowledge of the underlying schema and be brittle to future changes.

My particular usecase utilises text to store long hashes, so it would be ideal to treat them as unique - and I assume the same would be true for the plain text uses in the examples too.

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