If anyone else stumbles on this post and has a similar problem then
it's worth noting that the value field was a varchar doing an numeric
range evaluation on it. Even though it does in fact work some times
(mysql), you're better off hooking the save() method on a model and
converting the value to
Thanks Chris, I've looked at it a little, but we're wanting something with
more capabilities than I've seen in satchmo.
I'm still trying to figure this thing out. I changed my urls entry to
(r'^shopbyrange/(?P[-\w]+)/(?P\d+)-(?P\d+)/$',
'djangoecomm.products.views.searchbyattributerange'),
to
> I'm building an e-commerce system and at the moment working on making the
> products easily searchable. But when I use a __range lookup, in some
> cases
I'm sorry I can't help you with your request but I thought I'd point out
that there is a project called Satchmo that aims to build an ecommer
3 matches
Mail list logo