The correct is to write search_fields = ('name',) with comma.
You are showing that the search_fields are not mutable.
2007/9/28, yish <[EMAIL PROTECTED]>:
>
> Ignore my post, I found the issue :-) User error of course:
>
> I defined my search_fields for my model as
> seach_fields ('name')
> ins
On 9/28/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> well, this i just don't understand. plenty of programming topics
> considerably more challenging than this are solved via listserv every
> day in the open source world. i'd rather have a public discussion
> incorporating everyone's needs,
Ignore my post, I found the issue :-) User error of course:
I defined my search_fields for my model as
seach_fields ('name')
instead of
search_fields ['name']
I incorrectly followed the standard for all the other admin class
settings:
list_display = ('username', 'email', 'first_name', 'las
well, this i just don't understand. plenty of programming topics
considerably more challenging than this are solved via listserv every
day in the open source world. i'd rather have a public discussion
incorporating everyone's needs, ideas and concerns, not just "you and
ben" deciding between
HI all,
New to Django, but I still did some triage to try finding out what was
going on and better understand the framework. I set a breakpoint
within django.contrib.admin.views.main.py and found I was getting an
"IncorrectLookupParameters" exception when I entered in a text query
string. I am
You are going to have to provide more information.
Stating versions of mod_python/mod_wsgi and the configurations/script
files used would be a start. Some example code of what triggers the
problem and any relevant Django configuration, plus, exactly which
version of Django or revision number from
On 9/28/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> p.s. long emails on complicated topicsdetails get murky. so i've
> labeled the four major questions {Q1-4} so we can further isolate where
> we do and do not see eye2eye. :)
Rather that descend in to another few weeks of multi-page
On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> Paul Davis wrote:
> >
> > As near as I can tell these are the main issues that don't seem to be
> resolved:
> >
> > 1. Balancing ease of use with power of use (Ie, Alice vs. Carol)
> > 2. Level of versioning: Model vs. Application vs.
Mario Gonzalez said the following:
> I haven't seen this before, I'll try it but IMVHO it seems a hack
> because you've got to generate a field and _then_ change the queryset.
> I think the queryset must be defined once and not after.
Actually, you don't - I just checked the formfield method of
On 9/27/07, Xan <[EMAIL PROTECTED]> wrote:
>
> Yes, I suspect you "will create" a foundation of something of this
> kind.
> Like python foundation but with django ;-)
>
> If you plan to create that, please consider to create european
> foundation. Always software foundations are of US. EU citizens
Mario Gonzalez said the following:
> I should have to write the all callback and I think that's not what
> I want. My proposal is if you've got a special queryset, just pass it
> trough form_for_model() method only. Then you haven't got to re-write
> all over again.
Rewrite what all over? All y
On 27 sep, 18:03, Collin Grady <[EMAIL PROTECTED]> wrote:
> Mario Gonzalez said the following:
>
> > I should have to write the all callback and I think that's not what
> > I want. My proposal is if you've got a special queryset, just pass it
> > trough form_for_model() method only. Then you hav
Mario Gonzalez said the following:
> In my DB I've got lot of users, each one with different groups and
> permissions, and I don't want to show them in my form. So, I want to
> pass a parameter in form_for_model() and I wrote a patch for that:
Just make your own formfield_callback, that's what it
On 27 sep, 16:25, Collin Grady <[EMAIL PROTECTED]> wrote:
> Mario Gonzalez said the following:
>
> > In my DB I've got lot of users, each one with different groups and
> > permissions, and I don't want to show them in my form. So, I want to
> > pass a parameter in form_for_model() and I wrote a pa
Paul Davis wrote:
>
> As near as I can tell these are the main issues that don't seem to be
> resolved:
>
> 1. Balancing ease of use with power of use (Ie, Alice vs. Carol)
> 2. Level of versioning: Model vs. Application vs. Entire database
> 3. Application of versions: v1 -> v2 -> v3 =? v1 ->
Hello:
I usually show forms using form_for_model(), however there's
something I think is missing. My model is something like:
class TransferFile(models.Model):
file = models.FileField(upload_to="/some/path/in/my/system/")
owner = models.ForeignKey(User, db_column="owner", db_ind
Paul Davis wrote:
>
> As near as I can tell these are the main issues that don't seem to be
resolved:
>
> 1. Balancing ease of use with power of use (Ie, Alice vs. Carol)
> 2. Level of versioning: Model vs. Application vs. Entire database
> 3. Application of versions: v1 -> v2 -> v3 =? v1 -
Hey everyone,
Hopefully I've read up enough to jump into this conversation, but if I
haven't then feel free to blast me as is appropriate. If I offend
anyone, try and remember I'm only trying to show my opinions on
different issues. And you're more than welcome to fire back. ;)
So for some reaso
Russell Keith-Magee wrote:
> It's not the _model_ per se - just a rendition of the significant data
> in the model.
a rose by any other name (but yes, i assumed you meant not the
actual textual rendition, but a data structure containing all the
database-relevant attributes of the model)
>>
On Sep 27, 2:28 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 9/26/07, Xan <[EMAIL PROTECTED]> wrote:
>
>
>
> > > Expect something like this in a few months. The problem for now is
> > > that we have no official place to put the monetary proceeds from
> > > something like that.
>
> >
Wow!!!
I think you have no clear to _how_ things will be done!: several
projects, different opinions, etc.
Ideal ambient for create a perfect (with deadlines ;-)) schema
migration
Regards to all of you,
Xan.
On Sep 26, 5:02 pm, Xan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just want to know what i
I have a project running on django trunk using mod_wsgi in dev and
mod_python in production.
In production translation gives the expected results, in my own code
and in the admin.
Dev is set up exactly the same way, the only difference is that it is
running mod_wsgi, but no strings are translate
On 27/09/2007, at 13.59, Josir wrote:
> Any comments or suggestion are welcome!
> Even if you have to say: you have no choice - you have to install
> apache...
Please do not post general help questions to the django-developers
mailing list; this list is only for discussion of Django's code. For
I'd like to run a Python / Django program as a init.d startup script.
The script line is:
python manage.py runserver 192.168.0.2:8181
The problem: when it runs it spits out messages to the console and it
stops the boot process until I type Ctrl C.
Is there any command or hack to simply run it i
On 27 Sep 2007, at 11:52 am, Russell Keith-Magee wrote:
> That sounds like the best approach to me, and would be consistent with
> the testing API. As for multiple models; I would suggest:
>
> ./manage.py dumpdata product.Category product.Vendor product.Order
>
> Again, this would keep everythin
On 9/27/07, David Reynolds <[EMAIL PROTECTED]> wrote:
>
>
> On 27 Sep 2007, at 1:07 am, Russell Keith-Magee wrote:
>
> > Sounds like a good idea to me. It would dovetail nicely with the
> > proposal from ticket #4656.
> >
> > Want to try your hand at a patch?
>
> Sure, do you think the way I sugge
Thanks John!
I think it is that i needed.
Regards.
Jose Jiménez López
Becario de Sistemas
FUNDACIÓN IAVANTE
[EMAIL PROTECTED]
Tel. 958 00 22 63
Este correo electrónico y, en su caso, cualquier fichero anexo, contiene información confidencial exclusivamente dirigida a su(s) destinatario(s)
On 27 Sep 2007, at 1:07 am, Russell Keith-Magee wrote:
> Sounds like a good idea to me. It would dovetail nicely with the
> proposal from ticket #4656.
>
> Want to try your hand at a patch?
Sure, do you think the way I suggested it working would be right?
ie:
./manage.py dumpdata product.Cate
On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
> > The latter, by comparing the signature of the models.py that you have
> > with the signature in the Evolution table. The evolution table
> > contains the signature of the last model that was sync'd; if this
>
Coming back to my (and not also) problem...
More exact information about original post:
* The DB is postgresql 8.2, but it could be anyone else (I mean I must
be multi cross DB-platform).
* I'm using Django on trunk.
* Actually I described something that is a multi-threaded backend
application...
Hi all!
I've a need to use some custom permissions in my applications. In
order to do that I used this snippet:
- http://www.djangosnippets.org/snippets/334/
It creates custom contenttype and sets custom permissions on it. So
far so good.
Yesterday I moved to the latest Django vers
On Sep 27, 12:52 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 9/27/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Sep 27, 6:18 am, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
> > I'm actually waiting for some code to be put up to
> >http://code.google.com/p/django-evolution/-
Russell Keith-Magee wrote:
> The latter, by comparing the signature of the models.py that you have
> with the signature in the Evolution table. The evolution table
> contains the signature of the last model that was sync'd; if this
> doesn't correspond to the current model, you need migrations to
33 matches
Mail list logo
