On 11/12/06, shaunc <[EMAIL PROTECTED]> wrote:
> Well, in "your email or username" I entered my email. (I get confused:
> presumably I don't have a "django" username, or is it my username here
> at google groups?)
It's in the "settings" link at the bottom of the page.
> So... I appreciate that y
hi,
in certain cases, django-postgresql creates duplicate indexes...
imagine the following model:
> class Item(Model):
>text = CharField(maxlength=200,unique=True, db_index = True)
when installing it, it generates the following sql: (manage.py sqlall)
> BEGIN;
> CREATE TABLE "y_item
I just read Brian's latest (?) blog entry on his full-text indexing
efforts
(http://blog.case.edu/bmb12/2006/08/merquery_summer_of_code_results)
and wanted to pitch in, however was unable to post comments to the
blog. As it's django development related, I'll just post it here
instead.
He writes h
> We do that, actually. If you take the time to supply a name and email
> address, it exponentially decreases the spam weight of the submission.
>
Well, in "your email or username" I entered my email. (I get confused:
presumably I don't have a "django" username, or is it my username here
at goo
Erm,
I've just refreshed my django install to rev 3954 (per object
permissions branch) and deiscovered that model inheritance seems to
work...
Is this right? Have you guys secretly injected model inheritance back
into the distro? Or is the per-object-permissions branch running from
an old versio
