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
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
