The 'problem' is not normalization. Of course the field used in relation aiki_sites.site_shortcut has a horrible name, is too long with its 255 characters, hard to understand...and yes, aiki need a cleaning in its tables.
The problem is our cycle of development: - when somebody see a program with 5 errors and 200 blueprint, he/she thinks: it works but this guys need a lot of help. The same person, over a program with 150 errors and 100 blueprint, only asks: but...does it work? - if we are more strict in error definition we can correct EVERY error in each release and concentrate efforts in SELECT new improvements. I wrote "SELECT" because we have more blueprint that we can develop.. Roger -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/994444 Title: widget_site in aiki_widgets should be id not string Status in Aiki Framework: New Bug description: The whole idea about relational database is to have connection between tables using primary and foreign keys. so this should be equivalent aiki_sites.id == aiki_widgets.widget_site right now widget_site is varchar(255) and all widgets have "default" in it. To manage notifications about this bug go to: https://bugs.launchpad.net/aikiframework/+bug/994444/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
