> >> I was trying to streamline the whole process and I felt the need to
> have the snapshot as a separate entity just like a reg_entry or a
> reg_portgroup is, that is, "registry::snapshot" with a bunch of functions
> like create, get, list_all etc. I think this might help in writing the
> whole
On Thu, Aug 10, 2017 at 2:54 AM, Joshua Root wrote:
> On 2017-8-10 04:59 , Umesh Singla wrote:
>
>> Hi
>>
>> I was trying to streamline the whole process and I felt the need to have
>> the snapshot as a separate entity just like a reg_entry or a reg_portgroup
>> is, that is,
On 2017-8-11 03:41 , Bradley Giesbrecht wrote:
I think Josh is referring to 3NF normalization (third normal form). I don’t
think this use case warrants this complexity. I think it is fine for two
snapshot id’s to reference the same port+variant combination. When a snapshot
id is deleted,