Opened 15 years ago

Closed 15 years ago

#406 closed defect (wontfix)

Storing extended properties like information as annotations?

Reported by: Jari Häkkinen Owned by: Johan Enell
Priority: major Milestone:
Component: core Version:
Keywords: Cc: jari@…

Description

There is reporter annotations stored as extended properties in the database. Would it be hard to create importers to import the extended properties as annotations instead. Is there pros/cons to store the extended properties as they are done today (think extended-properties.xml) or should annotations be preferred?

Change History (4)

comment:1 Changed 15 years ago by Nicklas Nordborg

Component: corepluginscore
Owner: changed from Johan Enell to Nicklas Nordborg

The annotation system is designed for flexibility. The extended property system is designed for performance. For example:

  • Getting the value of an annotation requires 2-3 extra queries per item, the values of extended properties are part of the item and requires no extra queries. The same is true for updates and inserts.
  • The annotations are full-fledged objects managed by Hibernate. Reporters are part of the Batch system and doesn't use Hibernate to the same extent. In other words, annotations are part of the Hibernate internal caching system and uses a lot more memory.

comment:2 Changed 15 years ago by Nicklas Nordborg

Owner: changed from Nicklas Nordborg to Johan Enell

comment:3 Changed 15 years ago by Jari Häkkinen

(In [2779]) Addresses #406. Removed references to annotations system since it cannot replace extended properties due to efficiency issues.

comment:4 Changed 15 years ago by Nicklas Nordborg

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.