<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>You are banned! :-)<br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">I'll probably get banned for suggesting this: process dictionary ;)<br><br>> Date: Sat, 22 Oct 2011 07:19:18 -0400<br>> From: freza@circlewave.net<br>> To: joelr1@gmail.com<br>> CC: erlang-questions@erlang.org<br>> Subject: Re: [erlang-questions] ets table instead of large record<br>> <br>> # Joel Reymont 2011-10-22:<br>> > I have a record of 80 fields or so.<br>> > <br>> > I would like to use an ETS table for each instance of this record.<br>> > <br>> > Each field of the record would become a separate key in my table.<br>> > <br>> > Are there any drawbacks to this approach?<br>> <br>> ETS tables are somewhat scarce resource, I'd consider using global<br>> table instead of having it per-instance. Other than that, can you<br>> tell more about expected access patterns, timing requirements and<br>> such? Things can get tricky if you need something that looks too<br>> much like transactions (but it's not impossible).<br>> <br>> BR,<br>> -- Jachym<br>> _______________________________________________<br>> erlang-questions mailing list<br>> erlang-questions@erlang.org<br>> http://erlang.org/mailman/listinfo/erlang-questions<br> </div>
<br>_______________________________________________<br>erlang-questions mailing list<br>erlang-questions@erlang.org<br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote><br></div></body></html>