<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>+1 on 2<BR>
<BR>
basically, agreeing with everything said about human readability over clock cycles<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Fri, 13 Jun 2008 08:36:57 -0700<BR>> From: cmickeyb@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] standardizing on uuid string formats<BR>> <BR>> +1 on format 2<BR>> format consistency at the database storage level will help<BR>> tremendously in writing consistency checkers.<BR>> <BR>> might also want to specify standard character set... we currently use<BR>> UTF8 and latin1 (at least in the mysql tables).<BR>> <BR>> --mic<BR>> <BR>> <BR>> On Fri, Jun 13, 2008 at 6:00 AM, Sean Dague <sean@dague.net> wrote:<BR>> > We have 3 serialization formats for a UUID<BR>> > * XXXXXXYYYYYYZZZZZZ....<BR>> > * XXXXXX-YYYYYY-ZZZZZZ....<BR>> > * binary packed version (used in the mysql assets table exclusively)<BR>> ><BR>> > This is definitely confusing. One of the reasons that we got here is<BR>> > that there never was really a defined standard, and things grew and<BR>> > changed over time. One of the reasons that we are still here is that<BR>> > until recently, doing database migrations between formats would have<BR>> > been a lot of crazy logic. I'm hoping that the Migration support I just<BR>> > put in (and switched both SQLite and MySQL over to) should fix part 2.<BR>> ><BR>> > So, back to part 1. I think we should declare a standard, and work<BR>> > towards getting everything in that standard. My suggestion, and<BR>> > preference here is form 2: XXXXXX-YYYYYY-ZZZZZZ... for the following<BR>> > reasons.<BR>> > * It's very user readable, and like the format that people have come to<BR>> > expect in the client viewer. As people like looking at their data in<BR>> > both xml and in the database, making it make more sense to them is<BR>> > probably a good thing<BR>> > * It's the native string format for LLUUID and GUID (system built in).<BR>> > Using another format means lots of converting back and forth.<BR>> > * It also occured to me this morning that the extra string in every<BR>> > conversion might account for some of our extra overhead.<BR>> ><BR>> > All opinions on the table are valid. I firmly believe that anything<BR>> > that gets our data more self consistant will help with maintainability<BR>> > in the project. Please throw in your views, and I'll queue this up for<BR>> > future work.<BR>> ><BR>> > -Sean<BR>> ><BR>> > --<BR>> > __________________________________________________________________<BR>> ><BR>> > Sean Dague Mid-Hudson Valley<BR>> > sean at dague dot net Linux Users Group<BR>> > http://dague.net http://mhvlug.org<BR>> ><BR>> > There is no silver bullet. Plus, werewolves make better neighbors<BR>> > than zombies, and they tend to keep the vampire population down.<BR>> > __________________________________________________________________<BR>> ><BR>> > -----BEGIN PGP SIGNATURE-----<BR>> > Version: GnuPG v1.4.6 (GNU/Linux)<BR>> ><BR>> > iD8DBQFIUm+ESamXem9TdyYRAmlmAJwIPbjgfk1KEPJ0uYDsyogoc+JgoQCgpl/q<BR>> > gGE0KcWqi/7TTpP7KHQcIoI=<BR>> > =hUsu<BR>> > -----END PGP SIGNATURE-----<BR>> ><BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> ><BR>> ><BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>