[#TRACK-35] Using better property-fields - Adaptavist Public Issue Tracker

Confluence Extension: Tracking Plugin

Using better property-fields

Created: 09/May/08 07:06 AM Updated: 09/May/08 09:07 AM

Component/s:

None

Affects Version/s:

2.3.1

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. os_property_types.JPG
(32 kB)

Description

« Hide

as i am currently looking a bit to improve general performance, i asked myself why you write everything (especially dates and integers) to the TEXT-Property in the os_propertyentry table.

Honestly I dont know whether it will perform much better but (what for should these fields be there otherwise ) i think it should be an improvement, maybe for a release v. 3.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

David Peterson added a comment - 09/May/08 08:57 AM

I'm unsure what you're suggesting as an alternative? There are basically only two options for storing data in Confluence - Bandana and ContentProperty. Both use Strings, so conversion is always taking place. If you have a better location, I'm happy to hear about it...

[ Permalink | « Hide ]

Frank Stiller added a comment - 09/May/08 09:07 AM

find attached the types found in the os_property-table. I just thought to use other key_types within the property-table, e.g. date_val instead of text_val for dates...

I am not indepth like you on how good that can be achieved. I have changed for the survey-plugin the type from string to text (on the ContentPropertyManager)... but this manager only provides these two types if i remember correctly.