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 :-P
I will try make one auth.py that works with the same schemas created
with default SA auth.py but I really am a newbie :-(
On 13 Jan, 18:09, Gustavo Narea <[email protected]> wrote:
> Hello,
>
> For Elixir to be supported, we need someone who knows Elixir and is willing to
> support it. It seems like we have people who likes and knows Elixir, but
> nobody who is willing to make TG2 support it.
>
> Want to jump in? ;-)
>
> Cheers.
>
> On Tuesday January 13, 2009 18:56:08 Helio Pereira wrote:> Hi all,
>
> > Why do you remove elixir from the turbogears 2? Elixir and SqlAlchemy
> > must walk together in TG2 :-P
>
> > PS: Elixir seems more understandable for newbies like me...
>
> > Regards,
> > Helio Pereira
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---
