Hi Ian
BTW, this is different to what shabda was proposing, which was doing
all-the-web type searches
Ahh, I got you.
I'm not very clued up with Java so solr, although I've built it to
work on 3 sites now with django, they're still single indexes. We've
got over 200 sites in house that we're l
Matt Davies wrote:
> Hi Ian
>
>
> I'm not very clued up with Java so solr, although I've built it to
> work on 3 sites now with django, they're still single indexes. We've
> got over 200 sites in house that we're looking for a compelte search
> solution for.
>
> I think solr is definately the way
Thanks for the tips Ian
Building this search solution is the next job on my every growing
list, I think I'll blog it as it'll be a really good example of
someone who is starting from the beggining with very little knowledge
:-)
On 03/10/2007, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> Matt Davi
Derek Anderson skrev:
> hey nis,
>
> 1) psycopg2 has been added as a backend
>
Any reason for not using my code (importing postgresql.py for both
backends) rather than having two source files which are identical?
Shouldn't we at least replace postgresql_pcycopg2.py with
from postgresql import
Hi Guys
It turns out that setting a field to "models.NullBooleanField(blank=True,
null=True,)" causes all sorts of bad things to happen as Django tries to
insert '' into boolean fields... I know that NullBooleanField should
probably not have these switches (I did it by mistake) but I am not su
Personally I haven't found the need for this, since I don't lay things
out like that.
However, using the new-ish urlpattern url() notation would be the go
here. Just bung a new kwarg on url.__init__() with a default of
something like None, ALL or *, that would optionally accept values
like GET, P
I've implemented multi-column ordering in my own projects, and don't
think it's that tricky to use (in the UI, implementation may be tricky
but not too tricky). I use multi-column ordering all the time in my
apps and most desktop apps, so I'd love to see it built into the
Django admin.
In terms o
Hi there,
I've just been looking at some of django's internals trying to get my head
round the backend refactor...
I seem to have no luck slicing oracle flavoured QuerySets. From reading the
source it seems that the limit_offset_sql logic is going to be moved to a
separate module (called query.py
Hello,
I've created a patch for make-messages.py to add app names to
django.po file. ( closed:wontfix #1668 )
With this patch, it creates a temporary html file with installed app
names first, then runs make_messages() and removes temporary file.
Index: make-messa
On Wed, 2007-10-03 at 18:45 +0700, Ben Ford wrote:
> Hi there,
>
> I've just been looking at some of django's internals trying to get my
> head round the backend refactor...
>
> I seem to have no luck slicing oracle flavoured QuerySets. From
> reading the source it seems that the limit_offset_sq
On Wed, 2007-10-03 at 14:30 +0300, Peter Nixon wrote:
> Hi Guys
>
> It turns out that setting a field to "models.NullBooleanField(blank=True,
> null=True,)" causes all sorts of bad things to happen as Django tries to
> insert '' into boolean fields... I know that NullBooleanField should
> prob
On 10/3/07, Simon Litchfield <[EMAIL PROTECTED]> wrote:
>
> However, using the new-ish urlpattern url() notation would be the go
> here. Just bung a new kwarg on url.__init__() with a default of
> something like None, ALL or *, that would optionally accept values
> like GET, POST, HEAD, etc.
Note
As far as I see, reversing url is getting URL for a view. Then, if
view has only one route, there's no need to provide HTTP method. But
if there are > 0 routes to the same view, we can add optional METHOD
option.
Examples:
{# typical usage: #}
Goods
{# exclusive usage, many routes t
overplus '"' is exist
*** django/utils/translation/__init__.py(revision 6447)
--- django/utils/translation/__init__.py(working copy)
***
*** 106,112
return real_deactivate_all()
def string_concat(*strings):
!
Lazy variant of string concaten
Well, so it's not a bug!
But it's an enhancement:: http://code.djangoproject.com/ticket/5673
Thanks a lot,
Xan.
On Oct 2, 8:49 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> As James says, it's not a bug. But I'd agree it seems a little odd, until
> you look a little more closely at the admin
On Wed, 2007-10-03 at 14:43 +, [EMAIL PROTECTED] wrote:
> overplus '"' is exist
Please file bug reports in Trac, rather than sending them to the list.
Otherwise they will just be forgotten.
Thanks,
Malcolm
--~--~-~--~~~---~--~~
You received this message bec
yes, because that is what django does with it's psycopg2 backend. (or
at least did, when i originally added psycopg2 to the branch) i'm not a
big postgres user, i don't know what the differences between the two
are, i didn't know why they had done so originally, so until i figured
it out i t
While looking through the db-backend settings, I found
autoindexes_primary_keys. This seems to be True for all other backends
than mysql and mysql_old.
The only place in the code that this is used is in
django/core/management/sql.py, where it is used to "manually" create
indexes for primary keys
To my knowledge MySQL has always created indexes for primary and Unique's
automaticly.
This probably being the reason why it doesn't need that option to be set in
the mysql db backend.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
On 10/3/07, Nis Jørgensen <[EMAIL PROTECTED]> wrote:
> While looking through the db-backend settings, I found
> autoindexes_primary_keys. This seems to be True for all other backends
> than mysql and mysql_old.
>
> The only place in the code that this is used is in
> django/core/management/sql.py,
On Wed, 2007-10-03 at 10:51 -0600, Ian Kelly wrote:
> On 10/3/07, Nis Jørgensen <[EMAIL PROTECTED]> wrote:
> > While looking through the db-backend settings, I found
> > autoindexes_primary_keys. This seems to be True for all other backends
> > than mysql and mysql_old.
> >
> > The only place in t
2007/10/3, Derek Anderson <[EMAIL PROTECTED]>:
>
> yes, because that is what django does with it's psycopg2 backend. (or
> at least did, when i originally added psycopg2 to the branch) i'm not a
> big postgres user, i don't know what the differences between the two
> are, i didn't know why they
Hello,
I'm just curious:
What is your (the developers of Django) attitude towards Python 3000? Since
this release will introduce backwards incompatible steps it will be a larger
step to handle for the Python community.
Will Django be migrated to Python 3000 soon after it is relased or stick for
On Oct 3, 6:23 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Oracle changes on the queryset-refactor branch are probably going to be
> about the last thing to land on that branch because it's very time
> consuming to test and work with for me.
It sure is--we tend to run only single tests du
On 10/3/07, Florian Lindner <[EMAIL PROTECTED]> wrote:
> What is your (the developers of Django) attitude towards Python 3000?
Please search the archives; this has been discussed before.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscr
Hi All,
I am working on a Retain Search for www.nominum.com This is a great
opportunity for the right person to join a growing privately held
company that is very profitable - quite unusual these days...
If interested please send a resume to me at [EMAIL PROTECTED]
Sr Software Engineer - Web U
Am Mittwoch, 3. Oktober 2007 schrieb Jacob Kaplan-Moss:
> On 10/3/07, Florian Lindner <[EMAIL PROTECTED]> wrote:
> > What is your (the developers of Django) attitude towards Python 3000?
>
> Please search the archives; this has been discussed before.
Sorry I've searched for "python 3k" and "pytho
Hi Mike --
Please direct posts of this nature to django-users; django-dev is used
to discuss the development of Django itself, not for job ads and the
like.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dj
Am Mittwoch, 3. Oktober 2007 schrieb Jacob Kaplan-Moss:
> On 10/3/07, Florian Lindner <[EMAIL PROTECTED]> wrote:
> > Am Mittwoch, 3. Oktober 2007 schrieb Jacob Kaplan-Moss:
> > Sorry I've searched for "python 3k" and "python 3000" both which do not
> > return results that are a real discussion abo
I think this is the answer you are looking for :)
acob Kaplan-Moss wrote:
> Yeah, it's gonna be a long road...
Guido's tool "2to3"[1] should make those boring syntax conversions
automatically and leave only juicy parts to human brains.
[1]: http://svn.python.org/view/sandbox/trunk/2to3/
On Oc
Which means there is a tool for converting the versions otherwise you
are going to have to maintain 2 code bases.
On Oct 3, 1:51 pm, Florian Lindner <[EMAIL PROTECTED]> wrote:
> Hello,
> I'm just curious:
>
> What is your (the developers of Django) attitude towards Python 3000? Since
> this relea
On 10/3/07, Florian Lindner <[EMAIL PROTECTED]> wrote:
> Oh sorry, I didn't really consider this a discussion.
There's nothing to discuss, really. Porting Django to Python 3 isn't
even a theoretical possibility until Python 3 is released in a
finalized form and all of the libraries we depend on (
tonnzor said the following:
> As far as I see, reversing url is getting URL for a view. Then, if
> view has only one route, there's no need to provide HTTP method. But
> if there are > 0 routes to the same view, we can add optional METHOD
> option.
Or just make people use named URLs, which is alr
Hi guys,
Thanks for the reply. So if my only recourse at the moment to execute
qs._get_data() and then work with a slice as a list..? If there's any way
around that I'd like to hear it, my models are in a legacy DB, and it's
HUGE!! Is anyone using some method to get round this at the moment?
Cheers
On 10/3/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> Hi guys,
> Thanks for the reply. So if my only recourse at the moment to execute
> qs._get_data() and then work with a slice as a list..? If there's any way
> around that I'd like to hear it, my models are in a legacy DB, and it's
> HUGE!! Is anyon
On 10/3/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> Hi Ian,
> OracleQuerySets currently do not have any slicing ability AFAIK, apart from
> returning a slice of the qs._result_cache list... in the backend refactor
> all of the logic for building the SQL is in a function called
> limit_offset_sql on
Hi Ian,
OracleQuerySets currently do not have any slicing ability AFAIK, apart from
returning a slice of the qs._result_cache list... in the backend refactor
all of the logic for building the SQL is in a function called
limit_offset_sql on the DatabaseOperations class. This is overridden in
oracle/
Hi Ian,
There was some funky code in the branch I'm using and query.py wasn't
getting the correct subclass of _QuerySet.
Ben
On 04/10/2007, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
>
> On 10/3/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Hi Ian,
> > OracleQuerySets currently do not have any slicing a
cool. looks like nothing that'll effect us. i've switched back to one
common postgresql backend.
danke. :)
Yuri Baburov wrote:
> 2007/10/3, Derek Anderson <[EMAIL PROTECTED]>:
>> yes, because that is what django does with it's psycopg2 backend. (or
>> at least did, when i originally added
39 matches
Mail list logo
