On 29.05.2010 19:23, Jannon Frank wrote:
This produces a validation error on MyModel because it is checking the
combined string (e.g. '1,2,5') against the list of choices, when the
intent is to have each of the values in the string checked
individually against the choices.
Is there any disagree
Hi,
creating the doctests for the intersection stuff, I stumbled across this:
# Let's find all authors that have created articles in all known journals
>>> [Reporter.objects.filter(article__journal__id__exact=journal.id) for
journal in Journal.objects.all()]
[[John Smith, Paul Jones, Mike Miller
Luke Plant wrote:
> On Friday 05 May 2006 12:47, Michael Radziej wrote:
>> Hi,
>>
>> what about providing class functions QuerySet.union(cls, qset_list),
>> QuerySet.intersection(cls, qset_list), both returning cls, such as:
>>
>> def union(cls, qset_list)
Luke Plant wrote:
> On Friday 05 May 2006 17:46, Michael Radziej wrote:
>
>> This seems to indicate that &-combining QuerySets fails if the
>> QuerySets contain joins to the same table. I might also just haven't
>> got enough sleep last night, and my brain is
> No, this is different. It's not a question of outer or inner join, and
> it doesn't look easy to fix. I'll post a ticket ...
see
http://code.djangoproject.com/ticket/1801
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Hi,
ticket 1803 implements a set like interface for union/intersection, such as
aQuerySet.union(otherQuerySet)
ticket 1807 implements my original idea under the name list_union,
list_intersection, such as
QuerySet.union(listOfQuerySets)
comments appreciated ;-)
Michael
--~--~-~--~
Luke Plant wrote:
>
> Now I'm not sure either, looking back at the posts :-)
>
> Some people (e.g. Joseph) were definitely thinking in terms of doing a
> UNION or UNION ALL in SQL. For 'UNION', I think the ORM constrains you
> to using a single model, and therefore a single table, in which c
Hi
I must say I'm really annoyed that you cannot use models interactively,
or pychecker you model. To circumvent this restriction, I propose to add
a module level attribute for model modules, such as
app_label = "applabel"
... I've created a patch for this, see the ticket
http://code.djangopr
Hi,
I need to be able to use models like this:
class Xlwzl(models.Model):
xl = IntegerField(primary_key=True)
wzl = IntegerField(primary_key=True)
(they are actually ForeignKeys, but this probably doesn't matter.
This is probably also a good start for ManyToManyFields with an
Am 10.05.2006 um 20:09 schrieb James Bennett:
> You'll probably want to read this and save yourself some time:
>
> http://www.djangoproject.com/documentation/faq/#do-django-models-
> support-multiple-column-primary-keys
This indicates that you could simply ignore the problem and add a
composi
Am 10.05.2006 um 21:27 schrieb James Bennett:
>
> On 5/10/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>> But I need this for an ugly existing database (tm) that I cannot
>> touch. And, of course, it's a ManyToManyField in very open disguise,
>> but it has a
lifeisgood wrote:
> If I have a models file
>
> class City(models.Model):
> # ...
>
> class Person(models.Model):
> # ...
> hometown = models.ForeignKey(City)
>
> class Book(meta.Model):
> # ...
> author = models.ForeignKey(Person)
>
>
> then select_related will allow me t
Hi,
Am 13.05.2006 um 02:26 schrieb Eugene Lazutkin:
> There is a ticket #1586 (http://code.djangoproject.com/ticket/1586),
> which within one month was closed twice already. I understand it was
> confusing. It prevented one application to override templates for
> another application. Personally I
Am 15.05.2006 um 00:07 schrieb Marc Boeren:
>
> Update: the known bug is solved, the complete patch is now:
> http://www.million.nl/file/marc/django/multi-select-
> relatedfilterspec.2.diff
Though I can't currently use admin pages at all, this looks cute. Why
don't you open a ticket and prov
Hi,
Django silently drops certain types of exceptions during exception
processing.
Now, while this is in general useful, it really obscures your bugs.
I'd propose to optionally log those exceptions to stdout when, say
settings.log_template_exceptions, is set.
What do you thing?
Michael
Malcolm Tredinnick wrote:
> At some point we start to drown in config settings. It's probably better
> to just "Do The Right Thing" here (first, decide what the right thing
> should be). Having a way to always show the exception (if possible)
> seems like the right thing to me.
>
> The patch in
Hey Malcolm,
I was not aware that this behaviour changed between minor versions :-(
You're right: after updating from 3.2.1 to 3.2.8 no problems.
Ubuntu breeze currently provides 3.2.1, dapper will provide 3.2.8.
Malcolm Tredinnick wrote:
> (1) If you are using a sufficiently old version of SQL
Ville Säävuori wrote:
> I saw Changeset #2905 ( http://code.djangoproject.com/changeset/2905 )
> today and I think that there would still be room for improvement here
> regarding of slugifying at least some non-ascii letters (like ä and
> ö, which are widely used in Europe and Scandinavia).
>
>
Nicola Larosa (tekNico) wrote:
>> /me makes another note to spend some serious time with BZR...
>
> Try spending some time with Mercurial, too. It's simpler, smaller and
> faster than Bazaar-NG, while also being written in Python, with a
> little C.
Hmm. I'm using git for django. There's a tool
Hi,
anyone of you going to EuroPython this year?
http://www.europython.org/
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developer
Luke Plant wrote:
> Also, 'follow' is sub-optimal -- you have to calculate (either by hand
> or automatically) the fields that you want to *exclude*, rather than
> pass in simply the ones you want to include. Maybe some utility
> function on AutomaticManipulator might help.
Here's my version ...
favo wrote:
> I hope someone can see the post because I don't want to repeat it.
> http://groups.google.com/group/django-users/browse_thread/thread/cb3d55413a92151a
>
> I think is easy to fix. anywhere we have the function in 0.91.
> Thanks.
I don't have a fix, but the patch in ticket 1821 might
Jay Parlar wrote:
> Just wondering what the procedure is for getting a patch accepted?
You hit it! It would be so nice to have some kind of process in place.
And not just random wait-and-see, as it is currently.
Currently, it's a lot easier for me to just patch django and not share
my patches.
Adrian Holovaty wrote:
> Ideas for improving
> this system would be much appreciated!
How about spreading the routine work with tickets?
I think you have some people within the non-committers who have a
sufficient deep knowledge of django andf also sufficient trust to
pre-handle tickets. You cou
Hi,
I'm curious how in this function the local variable 'opts' spontaneously
appears on stage. Looks like a bug, but I'm not an expert on meta class
programming. I found this by pychecker, so it might also be dead code.
Else, wouldn't it be self.opts instead?
class Model, line #292:
def _g
David Elias wrote:
> Well, AS in FROM clause is not support...
Not even in the equivalent form
SELECT ... FROM table_name alias
?
That would really suck. How do you do joins to "self" then?
Michael
--~--~-~--~~~---~--~~
You received this message because you a
James Bennett wrote:
> On 6/2/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
>> One issue would be what to name this
>> more-critical-than-CriticalValidationError validation error.
>
> FatalValidationError.
HeartAttack
;-)
Michael
--~--~-~--~~~---~--~~
You recei
Hi,
is this again just me :-), or has some checkin changed an error message
recently?
If I run the test suite, I get:
'invalid_models' module: Validator found 47 validation errors, 47 expected
==
Missing errors:
invalid_mod
Malcolm Tredinnick wrote:
> Michael,
>
> On Wed, 2006-06-07 at 11:11 +0200, Michael Radziej wrote:
>> Hi,
>>
>> is this again just me :-), or has some checkin changed an error message
>> recently?
>> If I run the test suite, I get:
>>
>> &#x
Hi,
I currently find myself needing something very similar to the validation
framework. It's best explained with an example:
There is a form that configures email forwarding. The form will not only
validate well-formedness of the target addresses, but it will also check
whether its domain rea
Hey Adrian,
Adrian Holovaty wrote:
> Michael, you have stumbled upon an idea that I've coincidentally also
> wanted to do since before Django was open-sourced! See
Very Nice ;-)
But have you checked how I'm doing this different?
- Since data that does not pass tese "advisory tests" can get into
Hi,
The docs say, a filter shouldn't raise an Exception. But this does
not indicate what would happen if a filter does raise one; it merely
says you shouldn't do this, so the result is unspecified.
Actually, during development I'm thankful when an exception turns
into a traceback, so that
Hi,
I wonder if there's a bug in the case that save() creates a new record for a
model without data.
That's what happens if there is data provided (i.e., attributes assigned)
(lines 158ff)
if db_values:
cursor.execute("INSERT INTO %s (%s) VALUES (%s)" % \
Hi,
Some time ago, I wrote something in this direction, it's a Template
subclass that escapes all variable nodes. I found that I don't use
it, but perhaps someone wants to build upon it. It works, but misses
a proper loader.
If you have a pre-formatted string, you have to turn it into an
Hmm. I see two different cases that get munched in the discussion:
a) You run data through some filter or inside a html tag where it shouldn't be
escaped.
For this, you (or the designer) need to specify this in the template.
b) Parts of the context are pre-assembled html or are already unesc
Malcolm Tredinnick wrote:
> What I would like to propose is that we create a tests/regression/
> subdirectory for these slightly more mind-numbing but important tests.
> Same sub-directory structure, etc, as the the modeltests/ directory, but
> not in any way intended to be examples of good model
Simon Willison wrote:
> I've written up a proposal for how we can implement auto escaping
> while hopefully keeping most people happy:
>
> http://code.djangoproject.com/wiki/AutoEscaping
GoodStuff! (tm)
Michael
--~--~-~--~~~---~--~~
You received this message
Malcolm Tredinnick wrote:
> Because of the way tests are imported in runtests, it is currently not
> possible to have a subdirectory of modeltests/ and a subdirectory of
> regressiontests/ with the same name (so, for example, I created
> regressiontests/one_to_one_regree/ ). If somebody wants to p
Hi,
I thought a little bit about your remarks and I think all your problems can be
solved.
Perhaps it's also a good idea to add an attribute `raw` to the class `escaped`,
so that
you can always access the raw string when it is necessary. In some
circumstances, such
as when you pass a complet
Hey Andrew!
adurdin wrote:
> Michael Radziej wrote:
>> adurdin wrote:
>>> Having the context aware of the primary escaping needs of the output is
>>> a nice idea, but as James Bennett pointed out, the template is what
>>> should be making the decision.
>
Adrian Holovaty wrote:
> On 6/20/06, Simon Willison <[EMAIL PROTECTED]> wrote:
>> I've written up a proposal for how we can implement auto escaping
>> while hopefully keeping most people happy:
>>
>> http://code.djangoproject.com/wiki/AutoEscaping
>
> I've gotta say, I don't like the concept of a
Adrian Holovaty wrote:
> On 6/20/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>>
>> You're against automatically quoting your data in the database driver?
>> Let's rip it out, bad magic that munges your data behind your back.
>>
>
> I fig
Hi Andrew,
it appears to be decided that Adrian won't include auto-escaping,
but I'd like to round-up this discussion so that we can gather
the pros and cons somewhere. I bet that this discussion will pop
up again ...
For as much as I see, the discussion looks pretty thorough. I
acknowledge your
Derek Hoy wrote:
> On 6/20/06, SmileyChris <[EMAIL PROTECTED]> wrote:
>> But it is an escaping issue.
>
> Isn't the most common use case for this the problem of people entering
> bad stuff into a form? In which case, regarding it as a validation
> issue seems good to me.
This is the perl-taint-a
[EMAIL PROTECTED] wrote:
> not true. no browser interprets a single "<" as a tag unless it has a
> valid tag name (and company) and closing ">" directly after it. only the
> most rudimentary implementations would blindly strip "<"s without looking
> at their context.
So, how exactly would you v
[EMAIL PROTECTED] wrote:
> noone said "forbid nothing". i said "you don't need to forbid all '<'s",
> which is what you proposed was a problem with a data validation take.
My point was that your approach restricts user input. "<" was a
simple example for this.
Not that, first, it's not really s
Am 22.06.2006 um 06:54 schrieb James Bennett:
>
> On 6/21/06, Tyson Tate <[EMAIL PROTECTED]> wrote:
>> Oh - I haven't heard of the magic_quotes fiasco. Do you have any
>> links or more information about this? If it blew up for the PHP
>> folks, I think I'd be prone to changing my position on the
Hey,
First, let me note that we're discussing one aspect of Django and
whether or not there is a sensible way to harden it agains XSS
exploits. It is not whether this or the other way is better ...
Now, I don't like to put the whole burden into the input validation,
since I believe
* Ther
Hi Jacob,
Jacob Kaplan-Moss wrote:
> 2. Methods exist somewhere to "translate" untrusted strings into
> "normal" strings given a particular format. Like Simon, I'm not sure
> how to spell this, but I'm sure a good syntax could be found.
I'm not sure I missed a point; is this, for html, the
Hi,
waylan wrote:
> I've been following this thread since the get-go with interest, but am
> a first time commenter here. Although I think the devs have a clear
> picture, I get the feeling that some participants in this discussion
> are geting input validation and output escaping confused which
Hi,
Within the FormField framework, Manipulators and FormFields have
a method `prepare()`, but it seems never to be called. I put a
raise ADKLASD into it ... haven't seen it pop up.
If generic views called it before get_validation_errors (as the
docstring of prepare suggests), it would be a good
Hi,
I'm confused by a comment of Adrian in ticket 1563:
> Because manipulators are going away, I don't think we should do
this.
I've thought that models will gain validation, but manipulators
will stay and provide an additional level of validation for stuff
that e.g. needs custom manipulators.
Hi,
Looking into django.contrib.auth.__init__, it seems that
load_backend() is called for each request when you need to access
the request.user object. Then, the backend module is imported via
__import__. Isn't that a little much of an overhead?
My application requires a login for every request
adurdin wrote:
> #2207 was closed as "wontfix", because Adrian said:
>
>> Because the automatic manipulators (in their current form) are going away
>> before 1.0, there's no point in adding this to Django.
> ...
Thanks, that explains quite a bit. #1563 is specifically about
custom manipulators
Malcolm Tredinnick wrote:
> The __import__() call does not reimport the module if it already exists
> in sys.modules. It works just like the "import" statement in Python (and
> reload() works like imp.load_module()). So, aside from a single
> dictionary lookup, there is no overhead to calling it m
Hi,
I propose to add a setting that makes cookies 'secure'.
The secure flag tells the browser to send this cookie only over
https. The idea is that https makes sure that the cookie does not
leak out to a domain that belongs to someone else, even when the
DNS has been tampered.
Since the authent
Hi,
Generic views set messages, but don't enable translation, such as:
if not request.user.is_anonymous():
request.user.message_set.create(message="The %s was updated
successfully." % model._meta.verbose_name)
This is only an example, there are other similar cases.
Shouldn't this get transla
Hi,
the cascading delete came to surprise for me, too. I'm quite familiar
with a range of relational databases, and none of them does cascading
by default. They usually forbid it by default. That's why I did not
expect it at all, and of course it happened during a demonstration,
nearly wi
James Bennett wrote:
> On 7/12/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>> If you allow Null, this is in my opinion a strong indication that
>> deleting the other end should not cascade but set Null.
>
> Whatever the default ends up being, whether it st
Russell Keith-Magee wrote:
> I've got a project at work that requires a formal test harness, so I thought
> I would kill two birds with one stone and spend some time adding a formal
> test framework for all Django applications.
Russell, that sounds great! It looks like everyone's reinventing
the
Hey Simon,
Simon Willison wrote:
> The best way of running tests against a Django application, to my
> mind, is to run a "fake" web server (i.e. one that doesn't actually
> bind to a port) around the application. This fake server acts as a
> test harness. Tests can then create HttpRequest o
Gábor Farkas wrote:
> regarding running a "fake" webserver.. did you look at twill?
But it does not allow to test against the context!
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gr
[EMAIL PROTECTED] wrote:
>
> To me, possibly due to my own moral failings :), the most compelling
> case is the one that speaks to developer laziness. With the nose-django
> plugin, nose does right now everything in your proposal, with the
> exception of finding non-doctests in models.py. In addi
DavidA wrote:
> I've been having a problem rebuilding my database from scratch via
> syncdb. I've tracked it down to duplicate constraint name. Here is the
> output from manage.py sql for my app:
> ...
> This used to work, I'm pretty sure, but I haven't rebuilt the whole DB
> from scratch for a lo
Hi,
I really appreciate your work, it goes all along my wishes--thanks a
*lot*, Malcolm!
I'll try to find some time in the next few days to test how my
existing stuff would look using autoescape.
I have looked in your patch only cursory, so my comments refer to the
general approach and no
Hi,
Am 16.07.2006 um 23:53 schrieb Martina Oefelein:
> Hi Malcolm,
>
>> (3) Auto-escaping inherits down through template inclusions. That
>> is, if
>> you extend a template that has auto-escaping enabled, you get
>> auto-escaping enabled (obviously the autoescape template tag can
>> control
>> t
around one of those handlers that provides a nice
> testing interface) should be sufficient.
It's nicer if you don't have an additional process since you can
start the debugger in your tests.
> The are only two other solutions that come to mind for me:
>
> 1) The templa
Malcolm Tredinnick wrote:
> On Sun, 2006-07-16 at 21:30 +0200, Michael Radziej wrote:
>> I'm more for 'escaped' and 'raw', but not really violently. This is a
>> minor issue, and I wouldn't like to get the work delayed by it.
>> Also ... I
Malcolm Tredinnick wrote:
> If you want to mark every "still needs cooking" string then you have to
> mark *every* string that comes into the system (a la Perl's tainted
> strings).
Nonono ... I just was talking about terminology. We need a term
for "safe" and "unsafe" strings. I take it as gra
Hi,
Am 18.07.2006 um 21:57 schrieb Jacob Kaplan-Moss:
>
> On Jul 18, 2006, at 2:19 PM, jay wrote:
>> I'm new, so I don't know how to submit a patch. Our developers have
>> completed the extract_data function in django.db.models.related. It
>> seems to work fine.
>
> See http://www.djangoproject
Am 18.07.2006 um 18:06 schrieb Daniel Poelzleithner:
>
> Malcolm Tredinnick wrote:
>
>> Damn. Your phrasing tipped me off to a case we need this more: RSS
>> feeds
>> and Atom content elements with type="html". :-(
>>
>> We might need a "mark as unsafe" filter for these cases (so that
>> {{
Hi,
I made up my mind and I think I have the solution (for the is_safe
terminology, django world domination, and all the rest :-)
* finalized *
So it's :
FinalizedString (replaced SafeString)
mark_finalized() (replaces mark_safe)
preserves_finalized (replaces is_safe as a function attrib
jeremy bornstein wrote:
> In some circles, "finalization" is what happens to an object immediately
> before it is GC'd, so this choice may end up being confusing. This is
> the case with respect to Java, for example.
Doesn't keep me from liking it, and Java is not python. Probably
each and eve
Hi Chris,
Am 19.07.2006 um 22:56 schrieb SmileyChris:
> Back on topic, I like finalization too (even though I cringe having to
> write the american Z version).
Yeah, but default TZ is Chicago, so ... I chose zee. Be glad that
you're not forced to spell 'aluminum' somwhere!
The Old Britain Emp
Am 20.07.2006 um 04:25 schrieb Todd O'Bryan:
>
> Is xml_escaped just too verbose? Seems very descriptive and
> unambiguous.
Do you mean
mark_xml_escaped for mark_safe,
XmlEscapedString for SafeString,
is_xml_escaped for is_safe (as function attribute)?
In the (long) discussion, this has alr
Hi Aurynn,
Aurynn wrote:
> Hi there, I'm getting some very odd behaviour when trying to use
> unique_together, foreign keys, and AddManipulator() all together on
> some of my models.
>
> http://rafb.net/paste/results/kIEaT886.html - Company model
> http://rafb.net/paste/results/V3XUxE96.html - N
Adrian Holovaty wrote:
> If your goal is to cut crontab entries from five to one, just create a
> single script that does the five things you need it to do; then point
> crontab at it. :)
But it would be fine for pluggable applications to make this
automatically! (I'm +1)
Michael
--~--~---
wnielson wrote:
> Sorry if this has been mentioned but I couldn't find any reference to
> it.
>
> Anyway, there seems to be an issue with custom save() hooks and the
> admin interface. When called from the shell .save() works as expected,
> executing code both before and after the call to super(
Am 25.07.2006 um 22:41 schrieb James Bennett:
>
> On 7/25/06, wnielson <[EMAIL PROTECTED]> wrote:
>> if not self.genres.all():
>> try:
>> genre=Genre.objects.get
>> (name='default') #default g
wnielson wrote:
> Still no go though. Even after removing the if not
> self.genres.all().count(), it is still not updating the ManyToMany.
I cannot believe this has got anything to do with the super call.
This is related to the many-to-many-relationship. I suggest that
you just try to add a genr
Adrian Holovaty wrote:
> I really want to be convinced to continue using setuptools, but I'm
> drawing a blank... Insights are appreciated!
How about bundling setuptools so that you don't need to download
it later?
Michael
--~--~-~--~~~---~--~~
You received this
Hi,
this type of questions, that seems to come again and again, can
be solved for example by having an ini-style file of deployment
specific settings somewhere and reading them in your settings.py
file. An example implementation is attached, and here's an
example of how the ini file could look lik
t, but it seems to be a flaky default to me.
>>
> So I think secure data should be stored separately from project
> settings. Maybe usename and password should be stored in separate file
> also. But others don't need to do so. And if username and password
> also be stored with
Steven Armstrong wrote:
> Why not just create a second settings file, call it settings_local.py or
> whatever, and at the end of settings.py do something like:
>
> from settings_local import *
Well (apart from Adrian has put out his word now ...), my problem
was that I had to build a debian pa
Gábor Farkas wrote:
> =
> class Owner(Model):
> name = CharField(maxlength=500)
> thing = ForeignKey(Thing)
> =
>
> now let's say you have a LOT of Things... like 5.
>
> now, when you call Owner.AddManipulator(), he's going to fetch the WHO
Hi,
I'm checking out the changes from the last three weeks in svn ...
seems like the test suite is a little bit different now ;-)
I can't say much about it now other than I appreciate all the
hard work by Russell, and that there's a nice test framework in
place now.
Only ... I find the naming o
Hi,
just in case it hasn't been noted:
The css on the web site is missing - /css/homepage.css gives 404.
wiki pages render black on black. etc.
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django devel
Russell Keith-Magee wrote:
> On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>> Partly on this topic: I would very much like to use sqlite in-memory
>> databases for testing, even though I use MySQL for deployment. The speed
>> difference is 10x. One way to do this is to have a TEST_DATAB
Russell Keith-Magee wrote:
> On 9/13/06, Hawkeye <[EMAIL PROTECTED]> wrote:
>>> Some tests for
>>> your patch wouldn't go amiss, though I realise it's a pain writing
>>> tests for code when you don't know if it's going to be used.
>> Unfortunately, I don't think I'll be able to find the time to wr
Hi Russell,
Russell Keith-Magee wrote:
> ...
> Obviously, simple changes are no brainers. However, if a patch is a
> deep change, I (as a developer) need to be convinced:
> 1) That the problem actually exists
> 2) That the proposed fix is the right approach to solve the problem
> (e.g., there are
Afternoon wrote:
> Just a quick note to say I've added a ticket and patch to modify
> django.views.defaults.server_error to use RequestContext instead of
> Context, thus making context-processor-generated context available to
> 500 pages.
This was discussed ago and rejected because building
Malcolm Tredinnick schrieb:
> What is the advantage of doing this? The only saving you're making here
> is the amount of data you are sending from your client to the database
> server. Since that is generally going to be no worse than over a local
> network, the difference between, say, 2K and 1.5
Afternoon schrieb:
> Ivan, you're right to note that I can supply my own view. I will do
> that.
>
> James, why are context processors not able to handle exceptions and
> fall back to basic output, i.e. return an empty dictionary?
Hmm, I generally prefer a good traceback instead of getting
miss
Hi Nikolaus,
Nikolaus Schlemm schrieb:
> hi,
>
> in case anybody else has been trying to include one2many-relations when
> serializing the "one" side, take a look at
>
> http://code.djangoproject.com/ticket/2843
>
> would be great if someone else could test this as well. thanks!
It wou
Malcolm Tredinnick schrieb:
> Interestingly, looking at QuerySet.iterator() and QuerySet.__iter__,
> they aren't synonyms. The point is that QuerySet.__iter__ iterates over
> the result of QuerySet._get_data(), which actually sucks everything into
> memory before iterating. On the other hand, Quer
Russell Keith-Magee schrieb:
> Ticket 2737 requests a feature where __exact=None would be interpreted
> as __isnull=True. This would fix all three problems I have described.
> The proposed patch isn't correct, but I feel the idea is valid.
My brain has been wired in SQL mode, perhaps for too long
Russell Keith-Magee:
> Sorry - I'm confused; Are you agreeing with the proposed change, or
> saying it contradicts your expectations? (I think you are agreeing - I
> just want to make sure)
My highest preference is to make __exact=None behave like WHERE
xxx=NULL, i.e. returning an empty set, aga
orestis schrieb:
> Does this caching of QuerySets live beyond one request ? I assume each
> thread gets its own cache, right ?
>
> For us poor users of shared hosting, where we're using multiple
> processes that are killed and respawned many times, this isn't very
> helpful...
>
> Unless I haven
Thomas Steinacher schrieb:
> James Bennett wrote:
>> On 10/16/06, gabor <[EMAIL PROTECTED]> wrote:
>>> would you use something in the db? (from what i know about transactions
>>> (very little :), they "solve" the potential conflicts by simply
>>> reporting an error-condition to one of the "writers
Hi,
I have to start with a little background.
There's the still interesting issue of what media type you give
to your pages and whether to use html4 or xhtml. Large part of
Django seems to use xhtml, and I like it somehow better than
html, so I use it and give to browsers that accept it
appl
1 - 100 of 400 matches
Mail list logo
