Database Config - Standard Attributes - v4.3 b1816

Archive mAirList 4.x (English)
1

Hi,

In mAirListDB -> Administration -> Configuration and then the Standard Attributes tab I added a new attribute.

I gave the name ‘Test Attribute’ and chose kind ‘Option list’.

I set the values as:

Unassigned A-List B-List C-List

And then saved, and restarted mAirList as instructed. When I opened mAirListDB again the attributes were seemingly not saved. Sometimes the attributes list is saved, but I couldn’t find a trigger (e.g. length of list, characters) that would cause it not to be saved.

I’m using a local mAirListDB and couldn’t see any entries in the System Log other than the normal Loading… entries.

Many thanks,

2

The problem has been reported in the German forum yesterday, along with a sample database. I will investigate it. I suspect a problem with the XML serialization. Thanks for reporting.

3

Hi,

We’re still trying out the v4.3 beta - now with a network PostgreSQL database (which we will use in production) instead of a local one.

I tried the standard attributes again and everything was fine. Has this been fixed? I didn’t notice anything in the changelog.

Many thanks,

Jim

4

Only SQLite seems to be affected.

The attribute configuration is stored as an XML document in the database, in a VARCHAR field with no specific length. For some reason, the driver truncates the string at 255 characters when retrieved from the database, which breaks the XML document.

I could easily fix this by changing VARCHAR to TEXT in the affected table - but this would require a mAirListDB schema upgrade, which I’m trying to avoid at all costs (it makes migrating from v4.2 to v4.3 much more difficult)! I’m currently investigating other possible solutions.

5

Can you please try build 1828 and check if the problem persists?

6

Sure - that makes sense.

I’ve set up some different standard attributes and values - the problem is resolved here for me on a local DB. :slight_smile: