Guid length in various providers
|
|
Some javascript/style in this post has been disabled (why?)
Hello, I was noticing that between different providers, there is a different
printing of GUIDs. For example, the SQLServerSpatial provider prints them to 36
characters strings without {} braces, whereas the ArcSDE provider prints them
to 38 characer strings with curly braces. What is the ‘standard’ for FDO? Is there a plan
to ‘natively’ support GUIDS in FDO?
_______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||
|
Some javascript/style in this post has been disabled (why?)
Hi Chris, There is no standard in FDO for
this. FDO doesn’t have its own GUID type and the two providers have dealt
with the types separately. But, I think these two providers follow the
conventions of the underlying servers. SQL Server Mgt Studio I think displays
the unique identifiers by default without braces whereas Arc desktop tools show
them with braces. We probably could define a
convention for FDO if you have a suggestion. Thanks, Orest. From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Hello, I was noticing that between different providers, there is a
different printing of GUIDs. For example, the SQLServerSpatial provider prints them to 36
characters strings without {} braces, whereas the ArcSDE provider prints them
to 38 characer strings with curly braces. What is the ‘standard’ for FDO? Is there a
plan to ‘natively’ support GUIDS in FDO?
_______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||
|
|
Some javascript/style in this post has been disabled (why?)
I’m not sure I really have a
suggestion, other than adding native GUID support to FDO… I see the argument on the
underlying providers, that at least makes sense. ESRI actually requires ‘{‘s
to be there when setting GUID fields (via strings!?) through ArcObjects. SQL I
believe uses something similar to a .NET Guid.ToString() function which leaves
off the braces.
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Orest
Halustchak Hi Chris, There is no standard in FDO for this.
FDO doesn’t have its own GUID type and the two providers have dealt with the
types separately. But, I think these two providers follow the conventions of
the underlying servers. SQL Server Mgt Studio I think displays the unique
identifiers by default without braces whereas Arc desktop tools show them with
braces. We probably could define a
convention for FDO if you have a suggestion. Thanks, Orest. From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Hello, I was noticing that between different providers, there is a
different printing of GUIDs. For example, the SQLServerSpatial provider prints them to 36
characters strings without {} braces, whereas the ArcSDE provider prints them
to 38 characer strings with curly braces. What is the ‘standard’ for FDO? Is there a plan to
‘natively’ support GUIDS in FDO?
_______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
