<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Coming in a bit from the side here,<BR>
<BR>
we have, for some time, discussed to separate out the binary blog out of the metadata for an entirely different reason, namely to be able to weed out binary duplicates.<BR><BR>
If there was a way for us to separate out the binary parts, into something like 'binaryassetId, hashData[256], binarydata' and then just have the asset table referencing that row, I think it would help a lot.<BR> <BR>
I realize it's a separate discussion, just chipping in my two cents.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR><BR><BR> <BR>
<HR id=stopSpelling>
Date: Sat, 14 Feb 2009 17:49:22 +0200<BR>From: tommi.s.e.laukkanen@gmail.com<BR>To: mmazur@gmail.com<BR>CC: opensim-dev@lists.berlios.de<BR>Subject: Re: [Opensim-dev] Please do not revert fixes without careful comtemplation<BR><BR>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>On second though we could keep the current structure and expose all fields also through AssetBase properties. Then we could save / load the AssetBase with nhibernate as a single object and leave out the Metadata property from NHibernate mapping. Does this sound good?</DIV>
<DIV> </DIV>
<DIV>regards,</DIV>
<DIV>Tommi<BR><BR></DIV>
<DIV class=EC_gmail_quote>On Sat, Feb 14, 2009 at 5:06 PM, Mike Mazur <SPAN dir=ltr><<A href="mailto:mmazur@gmail.com">mmazur@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex; BORDER-LEFT: #ccc 1px solid">Hi,<BR><BR>On Sat, Feb 14, 2009 at 4:05 PM, Tommi Laukkanen<BR>
<DIV class=EC_Ih2E3d><<A href="mailto:tommi.s.e.laukkanen@gmail.com">tommi.s.e.laukkanen@gmail.com</A>> wrote:<BR></DIV>
<DIV class=EC_Ih2E3d>> I was talking with mikkopa and he suggested we should create two tables to<BR>> cover AssetBase to solve this issue properly. Namely AssetMetadata for<BR>> metadata information and AssetData for blobs to avoid situation where we end<BR>> up accessing also the blob data just to read metadata.<BR><BR></DIV>I was hoping not to have to do that.<BR><BR>It should be straightforward to support the current<BR>AssetBase/AssetMetadata composition in the existing OpenSim data<BR>layers, but as sdague warned me earlier, by mapping multiple classes<BR>to one table I was entering a world of pain. Seems that's exactly<BR>what's happening with NHibernate.<BR><BR>The reason I introduced the AssetMetadata class is to supply metadata<BR>information only for some requests that Cable Beach, the new asset<BR>server, supports. Now I realize that this was probably a premature<BR>optimization.<BR><BR>Instead of modifying the DB schema, we could have AssetBase inherit<BR>from AssetMetadata, as I outlined before[1]. Alternatively, we could<BR>get rid of AssetMetadata altogether and store everything in AssetBase<BR>as before, splitting out the metadata sometime in the future when a<BR>use case warrants it.<BR><BR>What do you think?<BR><BR>Thanks,<BR>Mike<BR><BR><BR>[1] <A href="https://lists.berlios.de/pipermail/opensim-dev/2009-February/004918.html">https://lists.berlios.de/pipermail/opensim-dev/2009-February/004918.html</A><BR></BLOCKQUOTE></DIV><BR></body>
</html>