Basically, there are two technically different ways of modeling collections in hybris:
CollectionTypes
Think of CollectionTypes in hybris as a backpack mounted onto a type
By runtime, CollectionTypes are resolved into a Collection of a kind of item, such as a List of MediaModels
Can cause overflow, resulting in truncation and therefore loss of data
More difficult to search and lower performance
On the database level, CollectionTypes are a comma-separated list of PKs, so there is a maximum
RelationTypes
Create links between all kinds of types Create type-safe n-to-m relations: Only link such elements of the source / target type declared at the relation
Values for relations are stored in a separate database table
+Each value is stored in a separate table row
While trying to start my hybrisserver in debug mode I got the following error messages and hybrisserver stopped. I tried but not able to solve. Any help please.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_…
We have a rather major issue in our hybris implementation with missing data base entires. We have been getting "Entity Not Found" errors. It started rather randomly on last Monday. The records that are causing errors are in the database …
Can someone please explain the concept of converters and populators used in the Hybris? I was going through the concept of AddOns in Hybris but one of the points said "You can plug populators into existing converters without having to …