On Tuesday January 13, 2009 19:26:21 Helio Pereira wrote: > Can you tell me what is the difference between old schema for > tg_user_group: > """ > CREATE TABLE tg_user_group ( > user_id INTEGER, > group_id INTEGER, > FOREIGN KEY(user_id) REFERENCES tg_user (user_id) ON DELETE > CASCADE ON UPDATE CASCADE, > FOREIGN KEY(group_id) REFERENCES tg_group (group_id) ON DELETE > CASCADE ON UPDATE CASCADE > ); > """ > > and de new: > """ > CREATE TABLE tg_user_group ( > group_id INTEGER NOT NULL, > user_id INTEGER NOT NULL, > PRIMARY KEY (group_id, user_id), > CONSTRAINT tg_user_groups_fk FOREIGN KEY(group_id) REFERENCES > tg_user (user_id), > CONSTRAINT tg_group_users_fk FOREIGN KEY(user_id) REFERENCES > tg_group (group_id) > ); > """ > > In the sql side I see few changes to justify delete elixir template > from auth.py
It's not about that. We can't claim that we support Elixir while we don't have somebody who maintains Elixir in the TG2 template, somebody who makes sure it works in TG2 itself, somebody who makes sure it's supported in the packages used in TG2 apps by default (namely, repoze.who.plugins.sa and repoze.what.plugins.sql) and somebody who is willing to answer questions related to Elixir in TG2 applications. If we're not certain that it works and will continue working, we can't claim Elixir support and thus we can't have a switch to generate Elixir projects from the quickstart command. -- Gustavo Narea <http://gustavonarea.net/>. Get rid of unethical constraints! Get freedomware: http://www.getgnulinux.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
