#landon_api
hard ingotBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1483874218004185170
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
autumn wasp
hi! looking into this now
i actually don't know off the top of my head if we promise IDs to be globally unique - i think we do and even if we don't guarantee it the chance of a collision would be extremely small
is there more context behind your question?
cursive lynx
basically, I'm getting AWS Appflwo to extract fulls for the following objects (for now, maybe more to come) - customers, subscriptions, invoices, prices to load into our SQL DB. TO avoid large scans, when querying this data with athena, we take the new data and merge it into a 'current state' table. The data is merged into this table via a merge statement that assumed the IDs are unique. So, if they are not unique, I could merge the data from both account A and account B into the same line, if they share the same id (ex. sub_12345). Basically merge [data] into [currentstatetable] by matching on [hopefullyuniqueid]
autumn wasp
ahhh yep, subscriptions are definitely going to be unique per account within an org, and so the IDs would also be unique
cursive lynx
so are you confirming that the ids will be unique globally for all objects? or just so far confirming global uniqueness for subscriptions?
^that sounds more aggressive than I want it to 😆
autumn wasp
all objects are globally unique, yep!