Associative options for a select

[brandom]

Now we can pass an object to options if we would like a display value mapped to a database value for selects.

Example:

VARIABLE: {
    "name": "var",
    "display": "Enum",
    "type": "select",
    "multiple": true,
    "options": {
        "DB": "Database", "KEY": "Value", "DBVAL": "Display Val"
     }
}

[uded]

You just broke report types with database options.
I will test it, but you should rather do it via named array, like described here.

Let me test it, but I think it will not work.

[brandom]

Thanks for testing. I was unaware of the named array method, but it is a little verbose for my needs. Some of my filters provide 20+ options.

The code used in this commit actually works with both methods for a MySQL database. Please let me know if you discover any issues with other backends.

[uded]

OK, tested it and it breaks my AdoDB types since I was using purely the
named array as it was created in the first design.

I need to take a close look at this...

Pozdrawiam serdecznie,

:: Łukasz Rżanek

2013/9/6 brandom notifications@github.com

Thanks for testing. I was unaware of the named array method, but it is a
little verbose for my needs. Some of my filters provide 20+ options.

The code used in this commit actually works with both methods for a MySQL
database. Please let me know if you discover any issues with other backends.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/85#issuecomment-23905645
.