[katello-devel] key-value pairs for objects in katello db

Ohad Levy ohadlevy at redhat.com
Wed Aug 15 14:28:58 UTC 2012


On 08/15/2012 05:19 PM, Justin Sherrill wrote:
> On 08/15/2012 10:03 AM, Ohad Levy wrote:
>> On 08/15/2012 04:34 PM, Ivan Nečas wrote:
>>> On 08/15/2012 03:26 PM, Tom McKay wrote:
>>>> One of the design tasks for this sprint is to come up with a way to
>>>> associate key-value pairs to systems and subscriptions. This would be
>>>> similar to the system facts that exist. It would be nice to allow
>>>> these pairs to exist on other objects now or in the future as well
>>>> (eg. activation keys).
>>>>
>>>> Question: What is the best way to model this in the katello db? Joins
>>>> or something?
>>> We have already this in User model: see
>>>
>>>     serialize :preferences
>>>
>>> this serializes this parameters into blob transparently.
>>>
>> when you serialize you lose a few things
>>
>> 1. the ability to join
>> 2. the ability to filter in sql (you have to load it all, decode it
>> and do in memory search)..
>>
>>
>> Ohad
> With katello's implementation of elastic search it could alleviate some
> of those issues depending on the implementation.   Although I'm not
> entirely sure what you mean by 'the ability to join'.
yeah, i mean the ability to sort..

Ohad
>
> -Justin
>
>>> -- Ivan
>>>>
>>>> _______________________________________________
>>>> katello-devel mailing list
>>>> katello-devel at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/katello-devel
>>>
>>>
>>
>> _______________________________________________
>> katello-devel mailing list
>> katello-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/katello-devel
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel




More information about the katello-devel mailing list