The Postgres implementation requires stream IDs to be valid UUID implicitly.

[krzysztofreczek]

Since we are using uuid-ossp extension in the Postgres adapter here, stream IDs that are not valid UUIDs will not be accepted.

Currently, the API does not enforce that UUID requirement which causes a bit of confusion.

Proposal: We could relax the requirement and allow users to use the ID of their choice.

@kamy22, could you please share the error you have faced when trying to use a custom stream ID?

[ilkamo]

Sure, this is the error: error retrieving rows for events: pq: invalid input syntax for type uuid: \"df0b5eb35fc94a9f0c41ec347793659a8304aad6\""

[ilkamo]

The streamID as UUID is a big limitation because sometimes a hash of something could be a good streamID and it is impossible to use it if the library forces to use only valid UUIDs.

[m110]

Good point, we should rework it into varchar 👍

[ilkamo]

I submitted a PR: @m110 @krzysztofreczek https://github.com/ThreeDotsLabs/esja/pull/35/files

[krzysztofreczek]

Thanks, @kamy22, well done!

[krzysztofreczek]

Merged