The above post is in reference to Craig Ogg's post on using the
Mercurytide FullText searching.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
Thanks for the post! It would have taken me hours to figure out where
to start looking when this error first came up. I made the change to
my SearchQuerySet subclass instead and it works also. I didn't make
the change to SearchManager. My code looks like this if interested.
class
On Sun, 27 Apr 2008, simonbun wrote:
> So qs-rf hit trunk and was merged into nfa on the same day! That's
> excellent news, both for me and for django. Thanks so much for your
> efforts Malcolm (and Brosner for the quick merge)!
I'll second that. I've been running against the nfa branch. I
Awesome work. Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL
w00t!
Not sure where to point this out, but anyone using the full text
search implementation from Mercurytide[1] will get the following
error:
django/db/models/query.py
line c = klass(model=self.model, query=self.query.clone())
"__init__() got an unexpected keyword argument 'query'"
Malcolm Tredinnick wrote:
> I merged queryset-refactor into trunk just now. This was changeset
> r7477.
Thanks for all of your effort on this, Malcolm.
Malcolm's Amazon Wishlist:
http://www.amazon.com/gp/registry/registry.html?ie=UTF8=wishlist=1VB5A16R2KV0T
On Mon, Apr 28, 2008 at 8:32 AM, Juanjo Conti <[EMAIL PROTECTED]> wrote:
> Could you give me a url where new features are explained?
> Is this backwards compatible or should I svn up with care?
Well, there's the wiki page Malcolm linked up in his original post...
--
"Bureaucrat Conrad, you
Malcolm Tredinnick escribió:
> I merged queryset-refactor into trunk just now. This was changeset
> r7477.
Could you give me a url where new features are explained?
Is this backwards compatible or should I svn up with care?
Thanks
Juanjo
--
mi blog: http://www.juanjoconti.com.ar
malcom,
thanks much for your hard work on this bad boy!
I've already @ioubeer ya on twitter. so the next time you're in nyc,
i'm buying.
much appreciated, cheers!
On Apr 26, 11:29 pm, Prairie Dogg <[EMAIL PROTECTED]> wrote:
> Malcom,
>
> Thanks so much for your tremendous effort and
On Apr 27, 4:04 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I merged queryset-refactor into trunk just now. This was changeset
> r7477.
Thanks for all your hard work Malcolm on queryset-refactor, it's much
appreciated!
Regards,
Matt
Thanks Malcolm for this huge contribution! I switched a quite big live
project to the new trunk and it's working really well so far.
Cheers,
Julien
On Apr 28, 3:23 pm, simonbun <[EMAIL PROTECTED]> wrote:
> So qs-rf hit trunk and was merged into nfa on the same day! That's
> excellent news,
So qs-rf hit trunk and was merged into nfa on the same day! That's
excellent news, both for me and for django. Thanks so much for your
efforts Malcolm (and Brosner for the quick merge)!
regards,
Simon
Malcolm Tredinnick wrote:
> I merged queryset-refactor into trunk just now. This was changeset
Thanks for the great work!!!
On Apr 27, 12:04 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I merged queryset-refactor into trunk just now. This was changeset
> r7477.
>
> There are still a couple of enhancements to do, but I've decided they're
> not worth holding up the entire branch for.
Great! I tried trunk as of a few minutes ago with a moderately
complicated project I have using MySQL and everything seems to work
fine. Will keep testing it over the next few days and report any
problems.
On Apr 26, 11:04 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I merged
I wish god will pay you Malcolm. ;)
It's a great news for django community.
thanx
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
On Apr 27, 8:48 am, Thierry <[EMAIL PROTECTED]> wrote:
> What's the current opinion about integrating sql alchemy into the
> backend of django's ORM?
There's an active project to do exactly that hosted here:
http://gitorious.org/projects/django-sqlalchemy/
Some of the features in
What's the current opinion about integrating sql alchemy into the
backend of django's ORM?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
I was just thinking last night about how nice it will be to get this
into trunk and there it is! :) Now I'm thinking how nice it would be
for Malcolm to send me $10,000... will let you all know how it works
out.
Seriously - great work and congrats on what must be a relief to
finally get to the
Mmmm... model inheritance... multiple OneToOne fields mmm
Thanks for all your hard work, Malcolm! Beers are owed to you!
On Apr 26, 2008, at 8:30 PM, Prairie Dogg wrote:
>
> Malcolm: Sorry - it's late over here, didn't mean to mis-type your
> name.
>
> File this and previous under:
Malcolm: Sorry - it's late over here, didn't mean to mis-type your
name.
File this and previous under: damn-life's-work-with-faint-praise
On Apr 26, 11:29 pm, Prairie Dogg <[EMAIL PROTECTED]> wrote:
> Malcom,
>
> Thanks so much for your tremendous effort and success on this!
>
> You rock!
>
>
Malcom,
Thanks so much for your tremendous effort and success on this!
You rock!
On Apr 26, 11:04 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I merged queryset-refactor into trunk just now. This was changeset
> r7477.
>
> There are still a couple of enhancements to do, but I've decided
I merged queryset-refactor into trunk just now. This was changeset
r7477.
There are still a couple of enhancements to do, but I've decided they're
not worth holding up the entire branch for. I can just as easily do them
on trunk.
Thanks to everybody who reported bugs and tested things. Thanks
22 matches
Mail list logo
