#@Interest: Dev For the developers using
mystic kettle
boreal cobalt
out of curiosity why swap to ULID?
mystic kettle
because we are moving off of mongo -> postgres
median horizon
Finally
gilded pier
boreal cobalt
because we are moving off of mongo -> postgres
what for?
mystic kettle
and postgres does not have 12 byte id tags
because mongo is a pain and rly doesnt suit well based on our data structure
gilded pier
to answer the question, it wouldn't affect my app at all, but my project is pretty small compared to others.
it would be trivial to update to a new id type
mint vigil
because we are moving off of mongo -> postgres
finally
timid steeple
doesnt matter to me
prisma glen
Don't have any projects that actually rely on the api rn but had some in the past and i dont think they would break in any major way
dense idol
because we are moving off of mongo -> postgres
best news for 7tv i have heard in so long
zinc ibex
Out of curiosity: why ULID instead of regular UUID?
we use UUIDs with postgres at work and it works pretty well
is it the because of the - special character?
rugged shell
strings in, strings out. should have zero impact on my Emote Wall 
mystic kettle
Out of curiosity: why ULID instead of regular UUID?
we use UUIDs with postgres a...
UUID is not stored as a string in postgres, its stored as a 128bit integer
the the difference between uuid and ulid is that ulid is timesortable and shorter when u return it