On 12/27/05, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> 7. Allow custom auditing methods ''without'' having to create a custom view.
>
> I've seen a lot of people ask for this, and I have yet to see an
> explanation of how to do it ''without creating a custom view''. I've
> tried quite a few
On 12/28/05, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > Look at get_values - it will return only those columns that you specify
> > you want to get.
>
> Ah - thats the use case I was missing. I withdraw my suggestion.
I've updated the docs to point that out explicitly. Thanks for bringing
I think this is a non-issue. I worked on GPL'ed project with Dojo before
Dojo became dual licensed and got a response from Alex Russell that it is
possible despite FSF opinion. Additionally I got an explanation regarding
BSD projects:
http://article.gmane.org/gmane.comp.web.dojo.user/1976/matc
On 12/28/05, Tom Tobin <[EMAIL PROTECTED]> wrote:
> Thoughts? Am I just being paranoid? :-)
Hey - you're not being paranoid if they're _actually_ out to get you :-)
Seriously: As far as I can see, yes, you're being paranoid (caveat:
IANAL either)
>From http://dojotoolkit.org/community/licens
On 12/28/05, Tom Tobin <[EMAIL PROTECTED]> wrote:
> IANAL, but it is my understanding that one can
> only relicense code if the new license's terms are a superset of the
> old license's terms.
IANAL either, but my understanding, after reading AFL and BSD and GPL
is that AFL is basically BSD with
On 12/28/05, hugo <[EMAIL PROTECTED]> wrote:
> Look at get_values - it will return only those columns that you specify
> you want to get.
Ah - thats the use case I was missing. I withdraw my suggestion.
Thanks,
Russ Magee
Since the idea of incorporating Dojo as Django's AJAX toolkit was
brought up, I've been researching the toolkit; I must admit that I'm
bothered by statements from the project regarding its licensing on the
Dojo-interest mailing list -- specifically, claims by the project
about the Academic Free Li
>I can't see any occasion that DISTINCT isn't either redundant, or
>required by design as a result of the goals of an Object-relational
>mapper.
Look at get_values - it will return only those columns that you specify
you want to get. You need distinct=True there, if you want to get rid
of duplica
Hi Eugene;
I say it is an artefact of a relational world because the very fact
you are using an object-relational mapping means that a certain subset
of SQL queries are either impossible or non-sensical. I think the use
(or rather, the non-use) of DISTINCT falls into that category.
For example,
