I think it's mostly only my fork (and it's forks) that vary much from
trunk. I never got around to changing the framework to come in line
with the master branch I think because it didn't support everything
that was needed. Not sure if it does now however.
On Aug 12, 4:00 pm, Rob Hudson wrote:
>
Oh, and thats most likely my branch you're referring to Martin. I
implemented a lot of the panels, and went so far as adding crazy
monkey patching in some of them to catch some information I wanted.
http://github.com/dcramer/django-debug-toolbar/tree/master
On Aug 11, 11:38 am, Martin Maney wro
I haven't brought this up for quite a while, but ``to_field`` still
does not function properly (at least as of 1.1, I haven't noticed any
changes addressing it though). The issue is that anywhere you do a GET
lookup, it doesn't process the to_field properly::
# TODO: waiting on to_field f
I'm a bit late in here, and it seems we reinvented a wheel as well
(even tho we did this about a year ago), but recently just OS'd our
simply notices system [1]. I'm also +1 for including something like
this in trunk rather than using the current user messages. I had a
brief look at django_notify
al, the fact is it doesn't work as
advertised, and it is advertised.
You would have to talk to the author of newforms-admin, which I believe was
Brian Rosner. There is some special code for handling to_field lookups in
the admin.
[1] http://www.pastethat.com/LUYWh
David Cramer
On
I believe someone had linked a ticket before, but I was unable to find one,
so I went ahead and submitted it here:
http://code.djangoproject.com/ticket/11938
David Cramer
On Wed, Sep 23, 2009 at 6:41 PM, David Cramer wrote:
> As usual, my apologies for lacking context :)
>
> Th
The proposal per your email is more or less how django-notices works.
Sent from my iPhone
On Oct 10, 2009, at 12:53 PM, Tobias McNulty
wrote:
>
> On Sat, Oct 10, 2009 at 1:19 PM, Tobias McNulty > wrote:
>> Things that still need to be discussed/done:
>>
>> * Coming to consensus on what 3rd pa
I also don't think this problem is being addressed here. Yes you could
pass messages to the context, but you would lose the ability to
retrieve those variably. I believe storing it in the existing session
is the best appoach for django's builtin support.
Sent from my iPhone
On Oct 10, 2009, at 8
hould definitely be a factor in
the decision.
Sent from my iPhone
On Oct 12, 2009, at 9:39 AM, Tobias McNulty
wrote:
>
> On Mon, Oct 12, 2009 at 10:21 AM, David Cramer
> wrote:
>> I also don't think this problem is being addressed here. Yes you
>> could
>> pass m
better way to optimize it than
regroup. However, with doing this it'd be very important that it doesn't
clear the messages unless you're pulling it out. django-notices handles this
by popping out elements in the iter (I believe), so that if you don't pop
the message out, it'
r. It's no quicker
doing it internally than it is using itertools.groupby or regroup in a
template.
----
David Cramer
On Mon, Oct 12, 2009 at 1:32 PM, Tobias McNulty wrote:
>
> On Mon, Oct 12, 2009 at 2:02 PM, David Cramer wrote:
> > I'm -1 on adding .errors or whateve
lete sense.
----
David Cramer
On Tue, Oct 13, 2009 at 2:53 AM, Hanne Moa wrote:
>
> On Tue, Oct 13, 2009 at 09:27, Russell Keith-Magee
> wrote:
> > I'm just
> > noting that adding Django support for Python logging is also on the
> > cards for v1.2, and it se
I agree, this is 30 minutes of work to change the usage in Django, and it
should be done with the inclusion of the messages patch.
David Cramer
On Fri, Oct 16, 2009 at 1:08 PM, Tobias McNulty wrote:
>
> On Fri, Oct 16, 2009 at 5:10 AM, Luke Plant wrote:
> > I think thi
I'm with Luke on this for the exact reasons he describes.
Sent from my iPhone
On Dec 5, 2009, at 7:24 PM, Russell Keith-Magee
wrote:
> On Sun, Dec 6, 2009 at 10:28 AM, Luke Plant
> wrote:
>> On Sunday 06 December 2009 00:56:56 Russell Keith-Magee wrote:
>>
Really? Files definitely seem t
For us we definitely use this behavior, and I'm guessing this is about
to bite us in the ass. I would think a simple fix would be to have a
commit=False, and validate=True keyword arg. By default, validate is
NoInput, but if commit is False it defaults to False. Wouldn't that be
a simple enough bac
The first three have been huges ones with us. We're just now running
into the settings issue, but would love to see what people can come up
with for solutions (we dont have a good one). Glad to see multi db is
finally shipping, and excited to see what can be done for startup
procs.
On Jan 19, 3:26
MySQL, in this situation, would have to actually select a row to
return a result, so it's slower. If it was just select 1 as a from
table where indexed_value = N, it doesn't even hit the tables, just
the indexes.
It's definitely not more efficient, and probably just an oversight
somewhere.
On Feb
It's already been done orokusaki. The examples were (humbly) horrible
as well. No template usage, just generic HttpResponse. That's basic
Python, and docs > examples (in code).
On Feb 15, 11:52 pm, orokusaki wrote:
> -1 I think examples, broken or working, are very helpful for absolute
> beginner
I definitely would like to see this handled in Django, but not in the
way mentioned. I personally think there does not need to be an option
for what it raises. I think of this in the situations where find
methods return either a -1, or an Exception, based on which method you
call.
Now I can't come
On Apr 7, 4:47 pm, OSS wrote:
> Front-End Developer - Contract/Telecommute | 40-50/hour
>
> My client is a B2B media company and they are looking to hire a Front-
> End Web Developer for a few upcoming projects, ranging from an online
> publication development project to social media application
I just want to throw my 2 cents into the ring here. I'm not against a
fork, but at the same time I want to see the Django mainline progress.
However, let me tell you my story, and how I've seen the Django
development process over the years.
I started with Django 4 years ago. It was cool, shiny, an
Realizing my original statement I was regarding this thread, in this
thread, it's obvious that this has gone completely off track. I might
have to take back everything I thought about this being useful.
If you want to address a SPECIFIC concern, it makes sense to do that
under its own topic. Think
It's an import issue with your app unrelated to django core. Someone
here will eventually tell you to direct that to django-users, so you
might as well hop over there now.
On Jul 12, 4:31 pm, pacman wrote:
> Hi,
>
> I've upgraded our python from 2.4 to 2.6.5. When connecting to django
> server (
http://dpaste.com/hold/4541/
:)
On Jan 10, 8:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Updated paste:http://dpaste.com/hold/4539/
>
> Should be no problems now :)
>
> On Jan 10, 8:22 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > Code Source:http://dpaste.com/hold/4538/
>
What's the svn command for generating the diff?
On Jan 10, 11:07 am, Michael Radziej <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] schrieb:
>
> > Updated paste:http://dpaste.com/hold/4539/Thanks for your code, and I would
> > have good use for some
> improvements on select_related. But it's har
Any links to an example ticket so I can keep a normal format for what
im going to post? :)
On Jan 10, 11:40 am, "Honza Král" <[EMAIL PROTECTED]> wrote:
> On 1/10/07, David Cramer <[EMAIL PROTECTED]> wrote:
>
>
>
> > What's the svn command for generat
http://code.djangoproject.com/ticket/3275
Thanks :)
On Jan 10, 2:50 pm, Nikolaus Schlemm <[EMAIL PROTECTED]> wrote:
> > Any links to an example ticket so I can keep a normal format for what
> > im going to post? :)take a look at the tickets with patches:
>
>http://code.djangoproject.com/
Not quite sure what to write in terms of the documentation :)
On Jan 10, 4:07 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> On 1/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'd like this to become core functionality as I feel its needed.For that
> > to happen, you will lik
I can do the docs, but it'd be a great time saver if you could do the
tests. I'm up to my elbows in work at the moment so :)
On Jan 10, 4:37 pm, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> if you want me to write the docs or the tests, let me know. I
> could deliver within a day or
ng to look into it some more tomorrow, if anyone has any ideas let
me know.
On Jan 10, 5:45 pm, Michael Radziej <[EMAIL PROTECTED]> wrote:
> David Cramer schrieb:
>
> > I can do the docs, but it'd be a great time saver if you could do the
> > tests. I'm up to my e
I retract my statement, we had some other random server configuration
error that just happened to appear at the same time as us putting this
live :)
On Jan 10, 8:34 pm, "David Cramer" <[EMAIL PROTECTED]> wrote:
> It seems there are some issues with the code. Although I&#x
It still seems to have a bug when just doing .select_related(depth=1),
sometimes its filling the field w/ the wrong data, looking into it.
On Jan 11, 11:31 am, "David Cramer" <[EMAIL PROTECTED]> wrote:
> I retract my statement, we had some other random server configuratio
So a few things we've done to take our test suite from 45 minutes to
12:
1. Implement global fixtures
These get loaded after syncing just like initial data. Obviously this
is a massive speed up
as you only reload them in between transaction test cases.
2. Don't inherit from TestCase if you aren'
Can we please change this so it defaults to off, and just document how to
turn it on and in what situations you should turn it on?
In my opinion this default-on feature caters to a very specific audience,
and will cause a lot of unexpected behavior with other users.
Here is the tl;dr of an argu
urrent connection is very different
than a single operation.
On Thursday, February 28, 2013 at 1:40 PM, Michael wrote:
> On Thu, Feb 28, 2013 at 4:10 PM, Christophe Pettus (mailto:x...@thebuild.com)> wrote:
> >
> > On Feb 28, 2013, at 11:09 AM, David Cramer wrote:
>
A common behavior I seem to have is the need to tweak the settings
object for certain test cases. The other case is that in many cases we
were (are?) relying on settings being configured a certain way for the
Django tests to even work. I brought this up in #django-dev a while
back, but wanted to op
With a decorator approach here's what I whipped up:
(This is dry code)
def with_settings(**overrides):
"""Allows you to define settings that are required for this
function to work"""
NotDefined = object()
def wrapped(func):
@wraps(func)
def _with_settings(*args, **kwar
in _orig.iteritems():
if v is NotDefined:
delattr(settings, k)
else:
setattr(settings, k, v)
return _with_settings
return wrapped
--
David Cramer
http://www.davidcramer.net
On Thu, Nov 4, 2010 at 2:26
I was going to propose the same thing Santiago. Signals seem like the
ideal candidate to solve that problem.
--
David Cramer
http://www.davidcramer.net
On Fri, Nov 5, 2010 at 4:57 AM, Santiago Perez wrote:
>> * Settings that are internally cached. For example, anything that
>&
We have been working on a new version of the API these past couple of
months, and we're nearing a public release. I wanted to take this
opportunity to see if any of the heavy API users (specific needs, etc)
would like to chime in with what they want to see, and possible give
our docs/api testing to
We're going to be deploying a backwards incompatible change to all
"since" values in the API. Any endpoint which accepts this parameter
to use as a form of range pagination will now include the value sent,
as well as values before or after it (depending on the order).
For example, in the original
I have no idea how I've done this, twice.
On Feb 10, 2:16 pm, Alex Gaynor wrote:
> On Thu, Feb 10, 2011 at 5:14 PM, David Cramer wrote:
> > We're going to be deploying a backwards incompatible change to all
> > "since" values in the API. Any endpoint which acc
Check out django-startproject from lincolnloop.com
https://github.com/lincolnloop/django-startproject
Kill off all the server configs (though some of it might be cool, like
Fabric integration), and I think it'd make for a pretty good base to
work from if this were to go into core.
On Mar 13, 9:1
In our profiling we've also noticed the cloning to be one of the
slowest parts of the app (that and instantiation of model objects).
We haven't yet, but had been planning on exploring a way to mutate the
existing class in most circumstances, but haven't
dug into it too much yet.
On Mar 14, 11:16
Ticket speaks for itself:
http://code.djangoproject.com/ticket/10098
My vote is to reopen it, as this is very common, easy to implement,
and very unlikely that it would ever need deprecated.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
We hit this same issue in Postgres (it's definitely not MySQL
specific). I'm unsure of the solution or precise conditions we're
hitting it in, but I think by default we use READ COMMITTED.
On May 7, 3:28 am, Tomasz Zielinski
wrote:
> I think that get_or_create is still broken, despite this
> fix
Would it help (in PG-world) at least if the selects where in
savepoints as well?
On May 7, 10:09 am, David Cramer wrote:
> We hit this same issue in Postgres (it's definitely not MySQL
> specific). I'm unsure of the solution or precise conditions we're
> hitting it in, b
You sir, are my personal hero for the day :)
We had also been looking at how we could speed up the fixture loading
(we were almost ready to go so far as to make one giant fixture that
just loaded at the start of the test runner). This is awesome progress
On May 13, 4:57 pm, Erik Rose wrote:
> tl
Also, one thing I'm quickly noticing (I'm a bit confused why its
setup_class and not setUpClass as well), but this wont work with
postgres without changing the DELETE code to work like the test
runner's TRUNCATE foo, bar; (due to foreign key constraints).
On May 13, 9:42 pm, Davi
, you're still reliant that nothing was created with
signals that uses constraints. For us this is very common, and I can't
imagine we're an edge case there
On May 13, 9:42 pm, David Cramer wrote:
> You sir, are my personal hero for the day :)
>
> We had also been looking at h
x27;t correspond
to a fixture or a model in the same app.
--
David Cramer
http://justcramer.com
On Mon, May 16, 2011 at 9:09 PM, Erik Rose wrote:
> Woo, thanks for the constructive suggestions!
>
>> Also, one thing I'm quickly noticing (I'm a bit confused why its
>>
Is there a sensible to way "copy" databases in SQL? it's pretty
obvious with things like sqlite, but outside of that seems tricky. I
really like that idea, and you should definitely just be able to (at
the very least) run a unique hash on the required fixtures to
determine if a database is availabl
Here's my proposal, assuming it can be done:
1. Create default database.
2. Run a test
3. If a test has fixtures, check for, and if not, copy base table to
``name_``.
4. Start transaction
5. Run Tests
6. Roll back
I think that pretty much would solve all cases, and assuming you reuse
tons of
class EasyWin(object):
def process_exception(self, request, *args, **kwargs):
if not request.is_ajax(): return
impot traceback
return HttpResponse(traceback.format_exc())
On Jun 10, 1:11 pm, Daniel Watkins
wrote:
> On Thu, Jun 09, 2011 at 08:31:44PM -0700, Valentin Golev wrote:
> >
This is currently a problem all over in the Django codebase, and I'd
love to see a generic/reusable approach at solving this everywhere.
On Jun 14, 1:19 pm, Michael Blume wrote:
> In RegexURLPattern._get_callback, we attempt to fetch the callable named by
> the URL pattern, and catch a possible I
I'm not suggesting changing the behavior (again due to the
compatibility concerns), but I completely agree with the original
poster(s).
Also, in my experience it's a much less common case that you're
wanting an "I agree" checkbox in your form, versus a "Boolean" field
which can be positive or nega
We've been working on switching our test suite to use some new "super
fixtures", which are really just global, test-only initial_data style
fixtures. To implement this we attach to the post_syncdb, and set a
runonce-per-db flag (since it seems to be the only available signal),
but we hit some issue
why
> would the other fixtures rely on the initial_data?
>
> On Aug 18, 4:15 pm, David Cramer wrote:
>
>
>
>
>
>
>
> > We've been working on switching our test suite to use some new "super
> > fixtures", which are really just global, test-only i
I came across the need today to modify PhoneNumberField to allow for
International phone numbers. Doing so, it occurred to me, it'd be very
useful just to be able to swap out my phone number field with the
localized version based on whatever country was selected.
Has any thought/real-use happened
I received a nice lecture when I asked "why doesn't Jinja (a template
engine I use as an alternative to Django) include an intcomma filter,
its very useful" on the fact that intcomma is a [insert a bunch of
negative remarks here] name for the filter, and it's an
internationalization concept, not a
I suppose I'll chime in here since we actually wrote master/slave
replication code on Curse.
Our approach:
- read_cursor and write_cursor exist. write_cursor is what cursor
would point ot.
- get queries all use the read cursor
- saves all use the write cursor
- we had a list of database connecti
I'll agree Magus is harsh, but he's also helpful, and this isn't the
place to discuss this :)
On Jul 1, 11:40 am, "Rajeev J Sebastian" <[EMAIL PROTECTED]>
wrote:
> +1 to Tom, though magus
>
> On Tue, Jul 1, 2008 at 7:34 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > On Tue, Jul 1, 2008 at 4:25 AM,
I personally like the rendering methods being attached to the form, as
they don't make sense as a universal template filter/tag. I do
however, use a filter as "as_p" doesn't do much :)
On Jun 28, 8:33 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sat, 2008-06-28 at 06:12 -0700, ionut wro
I haven't read this over in too much detail yet (I just auto ignore
the 10k trac emails about it :P) but a few concerns:
- Is there a setting (e.g. settings.py) to restrict the maximum file
size in an upload?
- For test suites couldn't you while (xrange(n)) pass /dev/random or
whatever to make a
2, 2008 at 1:25 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 22, 2008 at 2:13 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
>>
>> I was using utf8_general. I'm swapping to utf8_bin to attempt to fix
>> it, but binary encodings cause problems as w
Sorry, to be more clear, that is an *exact* match on what is in the
database, but using the BINARY form does not return the result.
On Tue, Jul 22, 2008 at 1:45 AM, Malcolm Tredinnick <
[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2008-07-22 at 01:29 -0500, David Cramer wrote:
> [.
Recently I noticed a bunch of queries I was executing by hand (one's
which the ORM didn't support) were not being committed.
I dug into the docs, and it clearly states that the default
transaction mode is autocommit, and mysql's default transaction mode
is autocommit.
So, my question is, what's
gn deicision to make on how that should be approached.
On Wed, Aug 27, 2008 at 5:23 PM, Rock <[EMAIL PROTECTED]> wrote:
>
> Any progress on this patch David? I would be happy to take a look at
> whatever you have and perhaps help out with completing the patch.
>
> >
>
--
n Wed, Aug 27, 2008 at 6:15 PM, Alberto García Hierro <[EMAIL PROTECTED]>wrote:
>
>
> El 28/08/2008, a las 0:27, David Cramer escribió:
>
> > Really I'm stuck at an architectural point.
> >
> > I have database validation and synchronization done, and the admi
ple public fields.
On Thu, Aug 28, 2008 at 5:36 PM, Rock <[EMAIL PROTECTED]> wrote:
>
> To be clear, the syntax is:
>
> myfkey = models.ForeignKey(SomeClass,to_field="id")
>
>
> >
>
--
David Cramer
Director of Technology
iBegin
http://www.ibegin.com/
--~-
This sounds like a bug. I would submit a ticket for it.
On Sep 1, 6:42 am, Jochen Voss <[EMAIL PROTECTED]> wrote:
> Hello,
>
> with Django 0.96 I used a model which contained the following field:
>
> class ImageFile(models.Model):
> [...]
> fname = models.ImageField(upload_to=
owever full support for setting up and managing partitioned
> models need not be included at this time. (I plan to help add that
> later.) The interesting point is that support for related fields for
> the Composite Primary Key is not required in order to support this
> particular use
9-02 at 22:02 -0700, David Cramer wrote:
> > For anyone who's interested, it'd be great to meetup at DjangoCon to
> > go over a good design approach to composite fields.
>
> Take notes. There's going to be a lot going on at DjangoCon (including
> celebrating), so the
Does the error message pretty easily let you figure out what's wrong?
On Aug 31, 1:38 pm, Martin Ostrovsky <[EMAIL PROTECTED]>
wrote:
> Now I'm not sure if this is a bug worth squashing or more a case of if
> you're dumb, you deserve what you get but ... I erroneously extended a
> template with i
Ya, depending on how support is planned I may be able to remove some
of the composite pk hacks.
FYI the last patch I threw up didn't work in all areas, but I do have
it running on our staging environment now without issues (so far). The
code is only very slightly changed though.
On Sep 9, 8:10 p
I think that will work Malcom. One thing we'll need to deal with,
is .name, .attname, etc on these. It should act the same way on the pk
as it does on the multi-column field (because after all, this will be
just a wrapper). Right now .pks is just an alias for .pk.as_tuple or
something. I had it th
If you're not doing denormalization in your database, most likely
you're doing something wrong. I really like the approach that is
offered here.
For me, personally, it would be great if this could accept callables
as well. So you could store the username, like so, or you could store
a choices fie
I was digging through some code today, and I noticed imports are
happening within a lot of functions. It was my knowledge that it works
like so:
import in a function is the same as ruby's load or php's include --
its executed everytime the function is
import in a module outside a function is lik
ying DB platform won't support
> triggers, but wouldn't triggers be the preferred solution when they're
> available? That way there is no chance that changes can be made outside
> the scope of the denormalization, and hence no need to recompute the
> denormalized values.
>
s executing the subquery in sql to get the denormalized output).
On Sep 23, 4:19 pm, "Justin Fagnani" <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 23, 2008 at 12:52 AM, David Cramer <[EMAIL PROTECTED]> wrote:>
> > For me, personally, it would be great if this could acc
Just use Jinja if you want faster template rendering ;)
In all seriousness though, this sounds like an awesome optimization
which I think should be fair game for 1.1.
On Sep 24, 6:28 pm, Johannes Dollinger
<[EMAIL PROTECTED]> wrote:
> Am 25.09.2008 um 00:39 schrieb Manuel Saelices:
>
>
>
> > It'
CopiedField sounds a bit off, but otherwise I like the proposed additions.
On Thu, Sep 25, 2008 at 8:08 AM, Andrew Godwin <[EMAIL PROTECTED]>wrote:
>
> David Cramer wrote:
> > I would say ignore triggers on the DB level, until they've been
> > written in the fra
We launched the new iBegin.com yesterday, and congrats to Django we've
pushed over 600 req/s on a server shared with several other websites
and daemons (including sphinx and memcached).
BUT I noticed a huge issue right after launch with memory usage. It
was randomly spiking (and staying) high. Th
Also in regards to this, using a template is overkill in my opinion.
Especially if it's going to cause extra headaches.
I'll try out your recommendation for now, thanks Malcolm.
On Sep 28, 11:40 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sun, 2008-09-28 at 21:21
After miserably failing at making it possible to use a field
with 10k choices, I've decided to take a new approach in the admin.
Right now I'm writing up a widget which would take the m2m field (for
raw_admin_fields) and output it just as it would a foreign key, except
one input per line. This
It seems I was unbelievably blind and not seeing the spyglass icon on
M2M fields. Please ignore me :)
On Sep 29, 5:48 pm, David Cramer <[EMAIL PROTECTED]> wrote:
> After miserably failing at making it possible to use a field
> with 10k choices, I've decided to take a new appr
It seems theres some issues, and this may go outside of the scope of
the admin history log (I didn't dig into the code).
1) It looks like it could use a .select_related('content_type') as
it's doing a query for every content type, repeatedly even.
2) It's adding an ORDER BY on the .get()-like qu
Oh, and it's also selecting the user in that history log query and not
using it.. at least from the looks of it.
On Sep 30, 5:23 am, David Cramer <[EMAIL PROTECTED]> wrote:
> It seems theres some issues, and this may go outside of the scope of
> the admin history log (I didn&#x
At least part of it seems to be fixed here:
http://code.djangoproject.com/attachment/ticket/9083/getAdminLogRelated.patch
On Sep 30, 5:24 am, David Cramer <[EMAIL PROTECTED]> wrote:
> Oh, and it's also selecting the user in that history log query and not
> using it.. at least
I'm running into an issue when trying to pass a file-like object to
HttpResponse and telling it to label it as "application/xml"
def sitemap(request, sitemaps, section):
page = request.GET.get('p', 1)
fpath = os.path.join(settings.BASE_PATH + '/', 'cache/sitemap-%s-
%s.xml' % (section, pa
Thanks Graham, I'll check that out.
I was going to file a ticket for this, but it seems streaming isn't
really "supported" anyways, so I had to change the approach.
On Sep 30, 8:19 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Oct 1, 11:06 am, David Cra
ey or with composite pk. It provides 2
> methods:
>
> - use of oid field (works on sqlite, oracle, postgres <= 8)
> - composite pk (for mysql that provides no oid field)
>
> cheers,
> Eric
> >
>
--
David Cramer
Director of Technology
iBegin
http://www.ibegin.com/
Some of these changes I think are very valuable, especially CSS
classes. The formfield_kwargs I don't think is the right approach, but
possibly a method which could be called, as a lot of times I'm
overriding __init__ and it's quite messy, just to change the queryset
for a form.
I would personall
I think being able to specify permissions for the AnonymousUser is
useful, but hacking this in as a row in the database for User is not
the right approach.
I'm +1 for the ability to give permissions to anonymous users.
On Oct 24, 9:59 pm, "Dj Gilcrease" <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 2
have permissions set to it.
On Oct 25, 10:46 am, "Dj Gilcrease" <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 25, 2008 at 2:59 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> > I think being able to specify permissions for the AnonymousUser is
> > useful, but hack
What you're wanting is a GenericForeignKey. Check out the
django.contrib.contenttypes documentation.
On Oct 26, 9:48 am, "Calvin Spealman" <[EMAIL PROTECTED]> wrote:
> You could also have a common parent class for Robot and User, and use that
> as your foreign key type. Which type is referenced w
lds to all of
> these models which really -do not- need them, makes me a bit ill.
>
> I would be more than willing to help test your implementation if there
> is anything usable yet. This is one of the pieces that's getting me
> all twitchy waiting for it.
> &g
eral proposals earlier along on this thread, but
> obviously nothing solid. Did anything ever come from DjangoCon on this
> topic? What issues still need to be addressed in this design?
>
> On Thu, Oct 30, 2008 at 13:46, David Cramer <[EMAIL PROTECTED]> wrote:
>
>> It allo
I really like the idea of the explicit GET params passed.So I'm +1
especially on solution #3. I actually had never realized it wasn't
caching pages with GET params, luckily though, any pages where I use
this decorator don't fluctuate like that :)
On Nov 1, 7:51 pm, "Jeremy Dunck" <[EMAIL PROTECTE
While I've been working on composite primary keys, I also made a few
tweaks to the admin app. Most of these are related to the primary key
support, but one is an optimization.
I would post this as a patch, or a ticket, but I want to open this up
for discussion, and my django repo is so far from t
1 - 100 of 279 matches
Mail list logo
