Ticket #18 (new discussion)

Opened 2 years ago

Last modified 2 years ago

Allow extent methods and entity methods to have same name

Reported by: mscott Assigned to:
Priority: normal Milestone:
Component: All Components Keywords:
Cc:

Description

This hypothetical entity class definition should result in an extent method that returns the first query defined, and an entity method that returns the second query defined, even though they share the same name. 

class Foo(E.Entity):

    ...

    @extentmethod
    def q_something(extent, ...):
        return ...

    def q_something(self, ...):
        return ...

Also discuss this, so that ordering can be reversed: 

class Foo(E.Entity):

    ...

    @entitymethod
    def q_something(self, ...):
        return ...

    @extentmethod
    def q_something(extent, ...):
        return ...

Change History

06/05/06 14:34:39 changed by mscott

  • milestone set to 2006 August software release.

04/04/07 13:38:46 changed by mscott

  • milestone changed.

Milestone 2006 October software release deleted

04/04/07 14:03:58 changed by mscott

  • owner changed.
  • component set to All Components.

pobrien, do you remember what the specific use case for this was? I think it was something I was talking about for Sphyra but I can't remember.

It seems like something good to have, perhaps only for 3.1 and above, but if we don't have a real-world use case for it, why have a ticket for it at the moment?