Sorry, I'm confused. In the db from Malawi, the table is called categoryoptioncomboname with no underscore in front.
I also don't quite understand what the bad practice consists in - do you mean that refactoring (adding the missing name) will break backwards compatibility? Knut 2010/11/15 Knut Staring <[email protected]>: > 2010/11/15 Lars Helge Øverland <[email protected]>: >> >> Its not categoryoptioncombo but _categoryoptioncombo. Its a resource table >> and not part of the model > > You mean that it is "_categoryoptioncomboname" and not > "categoryoptioncomboname", and that this is a resource table, right? > In other words, a table that gets generated? > >> Adding extra columns to domain model tables is bad practice. > > Ok, but can you tell me where else the names are stored? In other > words, how to populate the database directly with hundreds of > optionscombos? > > Knut > >> Lars >> >> On Mon, Nov 15, 2010 at 3:38 PM, Knut Staring <[email protected]> wrote: >>> >>> It seems to me this table only serves to hide the name from the >>> categoryoptioncombo table. Isn't this just adding to the complexity >>> (and confusion) of the multidiemensional makeup? >>> >>> Could we not just add the name to categoryoptioncombo? >>> >>> Knut >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~dhis2-devs >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~dhis2-devs >>> More help : https://help.launchpad.net/ListHelp >> >> > > > > -- > Cheers, > Knut Staring > -- Cheers, Knut Staring _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
