Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 10 of 14 total |
Binary GUID's |
Sun, Jan 13 2013 10:25 PM | Permanent Link |
Mario Enríquez Open Consult | I've read on the Roadmap page about a new upcoming binary GUID datatype on version 2.13. Could anybody can explain me what this is about and what to expect? (Better index performance/more efficiente storage..)
regards, Mario |
Sun, Jan 13 2013 11:52 PM | Permanent Link |
Raul Team Elevate | Mario,
<< I've read on the Roadmap page about a new upcoming binary GUID datatype on version 2.13. Could anybody can explain me what this is about and what to expect? (Better index performance/more efficiente storage..) >> Not sure of exact reasons for doing this but i would guess same reasons you listed: - 16 byte storage instead of 38 - index and joins should benefit from both smaller key (for storage and comparison) as well as binary comparison (no text comparison considerations) - native MS guid compatibility (might be of more benefit for .net side) Raul |
Mon, Jan 14 2013 8:38 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Mario,
<< I've read on the Roadmap page about a new upcoming binary GUID datatype on version 2.13. Could anybody can explain me what this is about and what to expect? (Better index performance/more efficiente storage..) >> The benefits are pretty much what you say: less storage, more efficient comparisons. If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Mon, Jan 14 2013 12:15 PM | Permanent Link |
Mario Enríquez Open Consult | Tim,
We're about to begin development this week and rely heavily on GUIDs for primary keys, using EDB GUID datatype. I would like to know if there are any consideration we could take in order to migrate to the new binary datatype as painless as possible. Development is done with Delphi. regards Mario, |
Mon, Jan 14 2013 5:45 PM | Permanent Link |
Barry | >The benefits are pretty much what you say: less storage, more efficient comparisons.< Tim, Will the resolution be the same as with the current text GUID? (Same probability of collisions?) Barry |
Tue, Jan 15 2013 11:33 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Barry,
<< Will the resolution be the same as with the current text GUID? (Same probability of collisions?) >> Yes, exactly the same. The only difference is that it won't be converted into text. Tim Young Elevate Software www.elevatesoft.com |
Tue, Jan 15 2013 11:35 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Mario,
<< I would like to know if there are any consideration we could take in order to migrate to the new binary datatype as painless as possible. >> The only difference will be the Delphi TField type - the binary GUID will use a TBytesField instead of a TGUIDField (descended from TStringField). Unfortunately, there is no Delphi TField descendant for binary GUIDs. If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Tue, Jan 15 2013 5:02 PM | Permanent Link |
Mario Enríquez Open Consult | Tim,
Thanks for the heads up! TByteField is the issue I was worried about, since we work with persistent fields switching from TGUIDField to TBytesField could get time consuming. BTW, if it is ok with you, I'll be glad to be a Beta tester for this feature, son we can implemented this functionality in our app from the beginning. regards, Mario "Tim Young [Elevate Software]" wrote: Mario, << I would like to know if there are any consideration we could take in order to migrate to the new binary datatype as painless as possible. >> The only difference will be the Delphi TField type - the binary GUID will use a TBytesField instead of a TGUIDField (descended from TStringField). Unfortunately, there is no Delphi TField descendant for binary GUIDs. If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Thu, Jan 17 2013 11:50 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Mario,
<< BTW, if it is ok with you, I'll be glad to be a Beta tester for this feature, son we can implemented this functionality in our app from the beginning. >> It's actually almost done, but I'll have to revisit why it wasn't completed. Many of these features that are on the roadmap have been, at least, started or mostly completed in the engine but have been delayed due to one or more nagging roadblocks to completion. If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Thu, Jan 17 2013 12:09 PM | Permanent Link |
Raul Team Elevate | Tim,
Are you planning to surface an ability to query this directly using SQL ? (would need some text to binary conversion/cast functions or ability to specify hex valued for binary). Raul On 1/17/2013 11:50 AM, Tim Young [Elevate Software] wrote: > It's actually almost done, but I'll have to revisit why it wasn't > completed. Many of these features that are on the roadmap have been, at > least, started or mostly completed in the engine but have been delayed > due to one or more nagging roadblocks to completion. |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, May 14, 2024 at 07:14 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |