I’ve used UUIDNumber with the same assumption that it was faster. But I never did any benchmarking. This is early helpful and interesting. Thanks Matt.
@angelostsa Жыл бұрын
Great idea to put those two under stress! Very useful insights!
@bradstanford211 Жыл бұрын
That's flippin' sweet. I much prefer hard data for creating best practices. Thanks for doing the work.
@ianjempson4687 Жыл бұрын
Thanks for that. The general consensus has usually been that the numeric approach is faster, but that's always been anecdotal. So it's nice to see a more rigorous approach to confirming or debunking that. Given the problems involved with numeric UUIDs in FileMaker when querying though OData, I'm not seeing any reasons why I would want to use numeric UUIDs in place of text.
@navarre.training Жыл бұрын
I also thought the consensus was that UUIDNumber was faster. I'm hoping that someone else has done tests to disprove some of what I found, or elaborate on it. I didn't know about the OData thing - thanks for that.
@siegfriedbarfuss93793 ай бұрын
What’s missing is what was the version of FileMaker and the host OS version. Also UUID needs to check uniqueness due to its implementation of pseudo randomness etc…
@navarre.training2 ай бұрын
That's a good point about the host and OS version. I haven't observed large differences in basic function like this across versions or platforms though - just small differences. If the UUID function checks for uniqueness, what does it check against? I figured it was just psuedo-random, and because the number is so large (3.4 x 10^38) the chance of duplication is effectively zero for record sets below 10 billion. I always uncheck the box in the Validation to require uniqueness and made a video about that recently, because I have several reasons for avoiding that check box.