webadmin: Adding Ticket Types fails if Order > 10

[Norbert Unterberg <nunterberg@…>]

When adding or editing ticket types with the webadmin plugin, from ticket type #10 on, all new ticket types get the order number (id) of 10. When you delete one ticket type with the number 10, all other #10 types are removed, too.

Does the web admin module only support ticket type ids with one digit?

[Christopher Lenz]

Why in the world would you need more then 10 types of tickets? ;-)

Anyway, I'll look into this.

[Norbert Unterberg <nunterberg@…>]

Actually we did not need 10 ticket types, we only needed 8 ;-)

When you add new types and delete the old ones, the number always increases, so when you are fiddling around with ticket type for some time, you quickly get numbers above 10 since ids of deleted ticket types are not reused.

And the ticket types are used for hardware project tracking and are something like Improvement, Layout, Development, Quality Control, Manufacturing etc. I guess we could have used ticket custom fields, but the ticket type was just there with no extra effort.

[anonymous]

It's not just ticket types. It's any AbstractEnum. First of all, the options should probably be sorted in the table by numeric order rather than lexicographic. Also, things break horribly if trying to add anything more than 10 options to any AbstractEnum. I haven't been able to figure out why yet.

[hyuga@…]

The problem seems to arise, at least in the case of 0.10dev that cast has not yet been properly implemented in sqlite_backend.py I made a simple implementation for my own purposes as:

def cast(self, column, type):
    return 'CAST(' + ' AS '.join((column, type)) + ')'

[Christian Boos]

Wasn't this one also fixed by r3690?

[Matthew Good]

Replying to cboos:

Wasn't this one also fixed by r3690?

Yeah, this is the same issue raised in #3490.

[Christian Boos]

(clearing report:35)