Thanks for the comments. But, I do not agree with your comments completely. First: There are lot of practical cases where the items/objects have to be identified distinctly eventhough there are 'N' number of items/objects with the same or similar characteristics.
Second: My idea is to use the 'range' concept for the initial storage. The attribute values do not change quite often for these items/objects. Even when the request arrives to modify one or few of them, we can create dedicated entries and divide the range into multiple entries with each of them for a subrange. productID:15-22 Now, if productId:18 is modified, the following will be done: - 1 dedicated entry with productId:18, with the updated attribute values. - 1 range entry with productId:15-17, with the existing/old attribute values. - 1 range entry with productId:19-22, with the existing/old attribute values. Do you still think, the requirement can be handled in a different way? --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
