hm. i use this approach and have secondary indexes configured on the columns if i need to do a specific search for an address.
alternately, in the user cf, if you wanted to be very uncool, but optimized for always retrieving the user email addresses, you could have the uuid for the user record and another row for uuid:email and each column is an email ... this way you can allow them to add as many as they want with key being the "type" as in the original email and the value being the email ... On Thu, Mar 10, 2011 at 10:15 PM, aaron morton <aa...@thelastpickle.com> wrote: > Slight variation is to use a standard CF and pack the column names, e.g. > "email.home" or "email.work" as column names. (Mentioned for completeness, > not the best approach)
