Field type CHOICES: Does it not save space?


#1

I just imported two text files – exported from my banking app – into Panorama X. Those text files have about 50 fields and are 1.7 MB and 3.1 MB in size.

Since some fields in these files are containing static data (repeating in each record, e.g. my name as account owner) I decided to set those fields to the type Choices. I was expecting a massive reduction of the file size — that used to be the result of this operation in Panorama 6.

But the size of my Panorama X databases did not change.

Is the Choices field type at the moment only a UI feature? Does it (still) not save space?


#2

Did you actually change the data type from Text to Choice? Just setting up the list of choices is not enough. It should definitely save space if there are repeating values, exactly like Panorama 6 did. You should be able to verify the size of individual cells with the sizeof( function. Unless there is a huge number of possible choices, the size of a choice field should be 1 byte. I just tested this to make sure, and it definitely worked. In the US Airports field I changed the Airframe Repair field from Text to Choice and the size decreased from 7.1 to 7.09 megabytes. That’s about right as the actual savings should be 10,788 bytes. I was also able to verify the change with sizeof(.


#3

Yes, I did, and sizeof( confirms a size of 1 byte for those fields.

So it seems I did not pay enough attention to the size of my database before the modification.

When I changed 6 of 50 fields to type Choices, the size of my second database decreased from 3.6 to 3.1 MB.

I am glad it works as expected.