On Jan 8, 10:13 am, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote:
> The two ways which are currently supported are:
> - full path addressing (including module the name in all targets)
> eg. parties = OneToMany('party.Party')
This works, though its rather verbose, since this is in another
project the full path is more like, 'myproj.model.party.Party'. Rather
verbose, but at least it works!
> - local (in the frame where the "source" entity is defined) references:
> eg. (in datafolder.py)
>
> from party import Party
>
> class DataFolder(Entity):
> ...
> parties = OneToMany('Party')
If you look at some of the modules, I don't believe I can do this
since several of them have circular references, which I believe would
likely cause circular import issues.
> > FWIW, improving the "target" resolving code is ticket #9
> (http://elixir.ematia.de/trac/ticket/9). I'll add a note to the ticket
> to make sure I try to get Ben's way of doing things to work when I
> tackle that ticket.
Awesome, maybe if Elixir kept a record of model names, and only
required the full module name in a case where there was duplicate
Elixir Entities.
Thanks for the pointer, after switching to the long module name
version, it does work.
Cheers,
Ben
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SQLElixir" 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/sqlelixir?hl=en
-~----------~----~----~----~------~----~------~--~---
