Why you need backward compatibility if we have upgrader, there are lots of new features that will not work without using upgrader so they are not backward compatible. And I'm taking about improvements that will not change everything even the API that it's not yet in use by no one.
And for this bug particular there is no connection between tables in aiki at all so the database will not guard integrity of data. And it's a bug, even if it's not show as error anywere, and fixing it will not brake anything and it will be backward compatible because it will not change and API, or the markup. On Sun, 06 May 2012 08:32:22 -0000 rg1024 <[email protected]> wrote: > Also the problem is that launchpad have only bugs .. > > > > This is not a problem if we use bug only to report bug. > If you want a improvement make it if is backward compatibility or > fill a blueprint if not. > -- Jakub Jankiewicz www: <http://jcubic.pl> twitter: <http://twitter.com/jcubic> blog: <http://jcubic.wordpress.com> -- 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
