On Sun, Jun 22, 2008 at 2:31 PM, MickaelC <[EMAIL PROTECTED]> wrote:
>
> Hi,
> It is a method to add tables to a model without having to manually
> launch the syncdb command in a shell?
1) django-developers is for discussing the development of Django
itself. If you have a 'how to' query, please a
On Wed, Jun 25, 2008 at 1:18 PM, Jeff Anderson <[EMAIL PROTECTED]> wrote:
> Here is another list:
>
> #6003 (from nfa-blocker)
> #6450
> #4148
Done. #6003 needs a little more discussion; I'd like to hear the
opinions of Brian and Joseph on that one; it's possible they have
already given the idea
On Wed, Jun 25, 2008 at 1:17 AM, Marc Fargas <[EMAIL PROTECTED]> wrote:
>
> But oviously, contrib apps should (to not say must) test their views to
> be sure that code released works! Hence, there should be a way for
> contrib apps to have an urls.py and test it.
Agreed. This is something we defi
On Wed, Jun 25, 2008 at 10:40 PM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
>> My preferred solution here would be to provide a way for test cases to
>> substitute a top level URL pattern object for the duration of the
>> test. For
On Thu, Jun 26, 2008 at 3:47 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> It appears that dumpdata includes things that syncdb will create
> automatically, and then loaddata attempts to insert them again,
> violating the unique constraint.
You've just found #7052. Changeset [7615] provide
On Fri, Jun 27, 2008 at 4:29 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El jue, 26-06-2008 a las 06:58 +0800, Russell Keith-Magee escribió:
>> >> My preferred solution here would be to provide a way for test cases to
>> >> substitute a top level URL patte
On Fri, Jun 27, 2008 at 3:23 AM, Marc Garcia <[EMAIL PROTECTED]> wrote:
>
> Could it be added to 1.0 maybe list? I think that those features are
> essential for developing not only international websites, also for
> developing non international websites for most countries (not US, of
> course ;).
On Fri, Jun 27, 2008 at 5:41 PM, David Reynolds
<[EMAIL PROTECTED]> wrote:
> Running with mysql backend created a few errors (I'm not sure if
> they're related so I've attached them in full, hope that's ok):
Hi David,
Thanks for doing this testing, but from the look of it, these errors
are all
On Tue, Jul 1, 2008 at 5:25 PM, Kenneth Gonsalves
<[EMAIL PROTECTED]> wrote:
>
>Let him be as rude as he wants, as long as he is there.
Lets stop this idea before it grows legs. One of the strengths of
Django is the community, and one of the reasons the community is
strong is because it is approa
On Wed, Jul 2, 2008 at 9:48 PM, vcc <[EMAIL PROTECTED]> wrote:
> I port MS SQL pyodbc backend (django-pyodbc) to newforms-admin r7671, tested
> on ubuntu 8.04 and with SQL Server 2005.
> I found sql server need convert boolean value to integer (BooleanField), so
> need add a new feature like 'n
On Fri, Jul 4, 2008 at 4:57 AM, Leo Soto M. <[EMAIL PROTECTED]> wrote:
>
> Hi all!,
>
> I've posted a patch[1] with a small refactor to some Field's
> get_db_prep_* methods. Basically, for non-basic field types, the
> database-prepared values is not computed by the Fields anymore, but
Hi Leo,
I'
On Sat, Jul 5, 2008 at 10:20 AM, Jason <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm a newbie and using Django in the context of Google App Engine.
Hi Jason,
1) Django-developers is a mailing list for discussing the development
of django itself, not for general user queries. Questions like this
Hi all,
I've been looking at #6017 and #5943 of late. These two tickets have
been around for a while; one of the biggest reasons that they have
taken so long to address is that they cover an area of Django where
the testing isn't automated - the behaviour of django-admin.py and
manage.py. As a re
On Tue, Jul 8, 2008 at 5:10 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Hi,
> i just updated to the lastest newforms-admin django, and my fixtures
> won't load anymore.
...
> to me this looks like get_or_create is broken in some way.
First off, unless you've actually confirmed that this
On Sun, Jul 6, 2008 at 11:39 PM, Joseph Kocherhans
<[EMAIL PROTECTED]> wrote:
>
> Dynamic choices become an argument to the form constructor. The
> argument is a dictionary of fieldname, choices pairs where choices is
> either the choices structure we currently use, or a queryset.
I have to say I
On Mon, Jul 7, 2008 at 10:08 PM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> One thing to watch for: I'm nearly 100% sure this won't work under the
> buildbot -- it looks like since the settings file is written in the
> same directory as the code you'll get conflicts between simultaneously
>
On Mon, Jul 7, 2008 at 10:10 PM, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> On Jul 7, 3:00 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
> The bash script appears to be used purely to set the environment
> variables. Is there any reason you can&#
On Mon, Jul 7, 2008 at 11:06 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 7, 2008 at 10:00 AM, Russell Keith-Magee
> I get 17 failures running on Ubuntu (gutsy), but maybe I'm missing something
> else needed for the tests to run properly? I just added the
>
On Tue, Jul 8, 2008 at 2:58 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Can I get a status report on how everyone feels about this date and
> the features on the alpha list?
Looking outside the alpha list, here's a quick update on the beta
tickets under my purview:
I'm predicting that #
On Thu, Jul 10, 2008 at 1:45 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Russell, if you can post the feedback for #7210 either here, or on the
> ticket(or on IRC), I'd try to take a look at fixing it.
The comments that matter are either on the ticket itself, or have been
posted to djang
On Thu, Jul 10, 2008 at 3:10 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I couldn't find a precise indication for that in the mailing list, but
> please point me out if I missed it.
>
> The roadmap clearly says that "nothing should rely on the deprecated
> oldforms". Does it mean that
On Mon, Jul 14, 2008 at 10:55 AM, Matt Wilson <[EMAIL PROTECTED]> wrote:
>
> I'm trying to figure out if I'm running the tests incorrectly, or if
> there are really are failed tests in the revision.
I'm not seeing any failure in my checkout of [7920].
Looking at the failures you are getting, it
On Mon, Jul 14, 2008 at 12:25 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
>
> Speaking of 2.3 compatibility, the tests don't run for me on 2.3 (which I
> just installed for testing purposes). I get:
...
> cmd += ''.join(' %s' % arg for arg in args)
> ^
> Synta
On Fri, Jul 18, 2008 at 3:57 PM, Rozza <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> This is a bump for ticket #5801 it was marked as accepted back in
> February but has not yet been applied!
>
> Apologies if this is against protocol - it just seems this simple
> patch has been lost amongst the many!
On Fri, Jul 18, 2008 at 8:47 PM, Rozza <[EMAIL PROTECTED]> wrote:
>
> Ah no problems!
>
> As there aren't any tests for the staff_member_required or even
> request.get_full_path() I wasn't 100% sure what the procedure would be
> as these are used through out Django.
>
> As it's such a minor change
On Sat, Jul 19, 2008 at 4:08 PM, James Bennett <[EMAIL PROTECTED]> wrote:
>
> Adding 'admin.autodiscover()' to the project's root URLConf fixes
> this; normally I'd just check in a quick change to the tutorial to
> indicate that this should happen, but it feels to me like the right
> thing to do h
On Sat, Jul 19, 2008 at 1:58 PM, Jason Yan <[EMAIL PROTECTED]> wrote:
>
> Re: http://code.djangoproject.com/ticket/7611
>
> The current situation is that if you create a new Django project and
> run the unit tests, the contrib.auth baisc tests fail due to missing
> templates. These templates are
On Tue, Jul 22, 2008 at 4:40 PM, Jason Davies <[EMAIL PROTECTED]> wrote:
>
> Anyone? Where's SmileyChris! :-)
If you've been paying attention, you may have noticed that the core
developers have been a little busy over the last week or so, pushing
1.0 alpha out the door.
I apologize for the fac
On Tue, Jul 22, 2008 at 7:21 PM, Michael Elsdörfer
<[EMAIL PROTECTED]> wrote:
>
> Previously, get_FIELD_display(), for a blank or unknown value of
> FIELD, return the value unchanged, e.g. say None or an empty string.
>
> After the change, it returns the automatically inserted blank choice
> (---
On Fri, Jul 25, 2008 at 10:30 AM, Devin <[EMAIL PROTECTED]> wrote:
>
> I've added a patch to #4788 that defines decorators for conditionally
> skipping tests and a usage of it per Jason and Russell's discussion in
> IRC about #7611.
>
> When tests are skipped, I'm raising an Exception SkippedTest.
On Fri, Aug 22, 2008 at 12:39 AM, crippledcanary
<[EMAIL PROTECTED]> wrote:
>
> I am working on http://code.djangoproject.com/ticket/6148.
> This includes a new option "db_schema" that's been added to a models
> meta class.
> It involves using a custom schema for any model that has this
> attribut
On Fri, Aug 22, 2008 at 4:12 AM, Nicolas Lara <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I am writing to let you know that I have posted the latest patches on
> aggregation support. All the planned features are implemented in the
> patch for #3566.
I would just like to take this opportunity to tha
On Fri, Aug 22, 2008 at 9:07 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> Shouldn't the ImproperlyConfigured form the backend's base.py
> get propogated up so that the real cause of the error (MySQLdb either
> missing or too old) can be seen?
This change certainly wasn't intentional. Looking at
On Sat, Aug 23, 2008 at 9:54 PM, Aidas Bendoraitis
<[EMAIL PROTECTED]> wrote:
>
> Hello folks!
>
> Django cares about model-view-controller separation, but the HTML for
> the widgets is hardcoded in the render method. I would propose to have
> overridable templates for the widgets, so every projec
Hi all,
In [8481], I committed a fix for #7443, dealing with a problem with
the timesince filter. About 20 minutes after I committed it, I became
aware of #8453, which is the same problem - except that #8453 suggests
that there has been a bigger discussion, and the ticket was closed
'invalid'. I'
On Mon, Aug 25, 2008 at 12:21 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> Hey Russ,
>
> On Sat, 2008-08-23 at 23:25 +0800, Russell Keith-Magee wrote:
>> Hi all,
>>
>> In [8481], I committed a fix for #7443, dealing with a problem with
>> the
On Wed, Aug 27, 2008 at 9:20 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-08-26 at 18:09 -0700, Cam MacRae wrote:
>> contrib.auth view tests fail if required templates aren't found. This
>> seems a sensible default in line with Russell's post [1]
>
> The problem with that ori
On Fri, Sep 5, 2008 at 11:36 AM, Chris De Vries <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> My name is Chris De Vries and I am involved with the IEEE student
> branch at the Queensland University of Technology in Brisbane,
> Australia [1]. I am organizing a program that encourages students to
> become
On Tue, Sep 9, 2008 at 7:10 PM, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've got some nice looking patches for this ticket, can someone give it a
> review? It looks well, has docs and testcases. I think this needs more than
> just my own look at the code.
>
> http://code.djangoproje
On Sat, Sep 13, 2008 at 1:35 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> I'd like to add support for fixture load/dump to deal with compressed
> (gzip) files transparently.
Something like #4924, perhaps? :-)
I'm not completely sold on the --compress option to dumpdata - there
are many option
On Sun, Sep 14, 2008 at 6:35 AM, Martin Diers <[EMAIL PROTECTED]> wrote:
>
> The answer is community packaging guidelines. Somebody needs to write
> or adapt an existing doc on how to package django apps using existing
> Python tools (which are excellent already), how to name them, etc.
Somebody
On Fri, Sep 19, 2008 at 6:05 PM, Bas van Oostveen <[EMAIL PROTECTED]> wrote:
>
> And would be as easy to implement, the possible usecases i've got is
> with a big fixture of a organism/protein database. This can be
> compressed very well and is only applied one, so no need to keep a 50+
> MB fixtu
On Sat, Sep 20, 2008 at 2:47 AM, HenrikV <[EMAIL PROTECTED]> wrote:
>
> If you imagine changing the table name of the auth.User table to
> 'account_user'. Should the groups relationship create a table called
> 'account_user_groups' or 'auth_user_groups' ?
I'm unclear if this is a user 'how to' qu
On Sat, Sep 20, 2008 at 6:13 PM, HenrikV <[EMAIL PROTECTED]> wrote:
>
> I am working on #3011, making the User model overridable.
Ok - do you think this might have been useful information to include
on your original query?
> I have a
> working patch, but
> if I set the db_table on the User model
On Wed, Sep 24, 2008 at 3:54 AM, Brian Beck <[EMAIL PROTECTED]> wrote:
>
> On Sep 23, 3:40 pm, "Adam J. Forster" <[EMAIL PROTECTED]> wrote:
>> Hi Eric,
>>
>> That's what I have done at the moment, but as you say it's a bit of a
>> hack and I'm not sure that I'm happy with it.
>
> I ran across this
On Wed, Oct 1, 2008 at 12:17 PM, Brett H <[EMAIL PROTECTED]> wrote:
>
> I cringe at posting this but.. there's a little forward slash that
> suddenly appeared on the Django website documentation url
>
> http://docs.djangoproject.com/en/dev//
>
> Is it just visiting or should I re-bookmark?
This i
On Mon, Oct 6, 2008 at 1:04 AM, SliceOf314
<[EMAIL PROTECTED]> wrote:
>
>> My personal preference for that ticket is that the annotation to say
>> which foreign keys to use should belong on the model for the
>> intermediate table, not adding to the declaration of the connecting
>> models.
>
> That
On Tue, Oct 7, 2008 at 7:17 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> I'd probably say that we bite the bullet and use 1.1 except then we
> should do what one of the Spanish Marc's has suggested in a ticket
> somewhere (could I be any less specific on the details, do you think?)
> and
On Thu, Oct 9, 2008 at 10:23 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Hi Devs,
>
> At DjangoCon it was mentioned that you were working on a process for
> nominating or approving 3rd party Django apps to be pulled in as
> official contrib apps. I'm curious if that's been worked out yet.
Merg
On Sat, Oct 11, 2008 at 7:59 PM, d. <[EMAIL PROTECTED]> wrote:
>
> Probably a simple, stupid error I'm making:
...
> What can I do?
> Can somebody please help? Do you need more information?
The Django-developers mailing list is for discussing the development
of Django itself, not for general user
On Sun, Oct 12, 2008 at 12:40 PM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
> On Sat, Oct 11, 2008 at 7:59 PM, d. <[EMAIL PROTECTED]> wrote:
>>
>> Probably a simple, stupid error I'm making:
> ...
>> What can I do?
>> Can somebody please hel
On Thu, Oct 16, 2008 at 11:13 PM, Jeff Anderson
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> #2507 has been accepted, documented, and there is a working patch. It's
> been used in production for some time.
>
> In the spirit of resolving the "issue" (it is a ticket after all) I see
> two choices: 1) Mer
On Sat, Oct 18, 2008 at 5:38 PM, Net_Boy <[EMAIL PROTECTED]> wrote:
>
> Hello
>
> am doing a new project and I want the user to register to the
> system, I use auth.user model
> when I call a form from it it only shows the Username and the password
> fields, I want to add the email field to it si
On Mon, Oct 27, 2008 at 8:05 AM, Andrew Godwin <[EMAIL PROTECTED]> wrote:
>
> class User(models.Model):
>username = models.CharField(max_length=255)
>email = models.TextField()
>num_photos = models.AggregateField("Photo", "fk:user", "count")
>num_all_photos = models.AggregateField(
On Tue, Oct 28, 2008 at 11:00 PM, Ilya Novoselov
<[EMAIL PROTECTED]> wrote:
>
> There was a ticket http://code.djangoproject.com/ticket/3371,
> concerning adding builtin filter to get dict value by key name.
>
> Jacob set resolution to wontfix, explaining that this filter would be
> out of django
On Wed, Oct 29, 2008 at 1:29 AM, Adam Nelson <[EMAIL PROTECTED]> wrote:
>
> Proposal:
>
> After running into numerous 'gotcha' type problems with django-contrib
> and django-hotclub on MySQL and looking at some of the MySQL code ,
> I'd like to propose that Django have an official minimum MySQL ve
On Thu, Oct 30, 2008 at 3:05 PM, ravirocks <[EMAIL PROTECTED]> wrote:
>
> Hey guys,
>
> May be this is easy for you. I am newbie to fixtures and Django unit
> tests. My problem is the named fixture is not being loaded. The
> fixture events_2.json in the code below is being ignored. Don't know
> wh
On Tue, Nov 4, 2008 at 2:58 AM, Bob <[EMAIL PROTECTED]> wrote:
> On a somewhat related note, is there some reason that 1.0.1 and 1.1
> milestones have not been created in Trac? It seems like triaging bugs
> into one of these releases should happen in Trac, not the mailing
> list.
Yes, there is a
On Tue, Nov 4, 2008 at 11:04 PM, mrts <[EMAIL PROTECTED]> wrote:
>
> Most other projects are managed by a priority queue and clear target
> set for releases ("this has to go into 1.0.1, this can wait until
> 1.0.2"). No problem if discussions on the mailing list are the
> preferred way of doing it
On Sat, Nov 8, 2008 at 6:45 AM, Valery <[EMAIL PROTECTED]> wrote:
>
> Hi all, @mtredinnick, @jacob, @wilson, @ubernostrum
>
> not sure if any "community boosts" are at all wanted here, but finally
> django is not for a closed circle of django-gurus and things are for
> the larger audience, isn't i
On Sun, Nov 9, 2008 at 5:56 AM, James Bennett <[EMAIL PROTECTED]> wrote:
>
> For 1.1, could we look into unifying the interface to
> ``response.context`` to avoid this sort of problem? Unless I'm
> thinking about this the wrong way, it shouldn't be too hard to
> differentiate dictionary-style acce
On Sun, Nov 9, 2008 at 6:40 AM, Eric Holscher <[EMAIL PROTECTED]> wrote:
> For my pony request, it would be really nice to have a way to get "user
> defined" context. This being things that were passed from views, set in
> template tags, (and maybe other places?). That is what the above code is
>
On Mon, Nov 10, 2008 at 4:53 AM, ershadul.hoque <[EMAIL PROTECTED]> wrote:
>
> I am Ershad, working as Software Engineer at Divine IT Limited,
> Bangladesh (www.divine-it.net)
> I am working using python and django, our mother tongue is Bengali ,
> language code bn-BD
> I want to translate django
On Thu, Nov 13, 2008 at 12:50 PM, Info Cascade
<[EMAIL PROTECTED]> wrote:
>
> The documentation says that implementation of one-to-one relationships
> will be changing...
Where does it say that? I can't find any reference in the v1.0 or
current development docs that say that OneToOne relationship
On Mon, Nov 17, 2008 at 11:20 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
>
> On Sun, 2008-11-16 at 18:11 -0800, [EMAIL PROTECTED] wrote:
>> In terms of signal overhead, the most likely case here is probably no
>> receivers, and in the signal refactor, that particular case is now
>> hugely
On Mon, Nov 17, 2008 at 12:21 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Well, Jeremy Dunck was kind enough to do a benchmark against the old
> system:
> http://groups.google.com/group/django-developers/browse_thread/thread/815f76ad7e823cbf/b008a757fbdefa2b
I knew about these. While th
On Tue, Nov 18, 2008 at 9:34 PM, zvoase <[EMAIL PROTECTED]> wrote:
>
> Hi,
>I think I might be speaking for a few people here who have kinda
> seen enough of the "olddocs" warning/message/admonition thing every
> time we search on the Django docs. It's been 2 and a half months since
> Django 1
On Wed, Nov 26, 2008 at 2:08 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> I'd like to officially drop Python 2.3 support in Django 1.1. Discuss.
I'm going to be the stick in the mud and say -0.
I don't have any particular love of or need for Python 2.3, but it has
taken u
On Wed, Nov 26, 2008 at 10:16 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> However, even saying Django 1.1 is the last 2.3-compatible version and
> we drop it afterwards gives us a reasonable 3.0 support timeline, since
> our timeframe doesn't really encourage any official 3.0 support for
On Wed, Nov 26, 2008 at 1:30 AM, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Tuesday 25 November 2008 01:02:03 Rob Hudson wrote:
>> Hi Django Devs,
>>
>> I saw that ticket[1] made it into the 1.1 list and I was drawn to
>> it. I have a project that will be doing some mass sending of emails
>> soo
On Mon, Dec 1, 2008 at 3:03 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> On Sun, 2008-11-30 at 23:51 -0600, James Bennett wrote:
>> Apologies for bringing this up past the 1.1 feature deadline, but
>> since this isn't a feature perhaps it'll be OK :)
>>
>> Currently, Django bundles a copy
On Mon, Dec 1, 2008 at 4:21 PM, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On Mon, Dec 1, 2008 at 12:45 AM, Russell Keith-Magee
> <[EMAIL PROTECTED]> wrote:
> I guess the thing that's bugging me is that this mostly seems to come
> down to historical inertia; we a
On Sat, Dec 6, 2008 at 3:16 AM, mrts <[EMAIL PROTECTED]> wrote:
>
> On Aug 11, 9:11 pm, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> I'd write more but I'll first wait for responses, file some tickets,
>> and think about what else Django could do to improve its cooperation
>> with App Engine...
On Tue, Dec 9, 2008 at 11:44 PM, Thomas Guettler <[EMAIL PROTECTED]> wrote:
>
> http://code.djangoproject.com/ticket/3896
>
> The initial question of this ticket was:
>
> Why is value not passed to the clean_%s function?
>
> Although the ticket is closed, this has not changed.
>
> I think clean
On Tue, Dec 9, 2008 at 9:24 PM, Christopher Allan Webber
<[EMAIL PROTECTED]> wrote:
>
> So, by now the primary problem with Django is not the lack of good
> applications. There are tons of good applications. The primary problem
> is that almost none of them work together. There are a few reason
On Tue, Dec 16, 2008 at 7:07 AM, David Cramer wrote:
>
> I'd like to propose the addition of some useful (and common) fields in
> the django core. Things like a JSONFied, YAMLField, HTMLField?,
> UUIDField, etc.
>
> A lot of these seem like common things people use, and while many
> examples are
On Tue, Dec 16, 2008 at 1:16 AM, David Reynolds
wrote:
>
> Hi,
>
> I've been attempting to keep this ticket inline with trunk for quite a
> while and it would be useful to get some feedback on it, or start up a
> discussion as to how it can move forward. Russell mentioned a while
> ago that it c
On Fri, Dec 19, 2008 at 4:30 PM, Evren Esat Özkan wrote:
>
> Hi,
>
> I was sent this message to the users group but nobody replied.
> So, may be here is the right place for my problem;
Please don't do that. Django-developers is for discussing the
development of Django itself. It isn't "second ti
On Sun, Dec 28, 2008 at 7:29 AM, Justin Bronn wrote:
>
> Ariel,
>
>> Is it a gis issue or an aggregation one?
>
> As I indicated in private correspondence, this was a matter of
> updating GeoQuery.get_columns to reflect Russell's aggregation
> changes. I've attached to #3566 a patch for Russell'
On Wed, Dec 31, 2008 at 8:43 AM, Justin Bronn wrote:
>
>> I'll be looking into this, this week.
>> Good news is: So far so good (But I haven't tried to mix geo aggregates with
>> new aggregates yet).
>
> OK, in the GeoDjango 1.1 mercurial [1], I've merged in Russell's
> aggregation branch and mod
On Sat, Jan 3, 2009 at 5:29 AM, Brantley Harris wrote:
>
> Having not been content with the state of Django migrations systems,
> I've created one of my own:
>
> http://www.bitbucket.org/DeadWisdom/migratory/
In the aftermath of DjangoCon [1], Simon Willison, Andrew Godwin and
myself started the
On Sun, Jan 4, 2009 at 4:28 AM, Brantley Harris wrote:
>
> On Sat, Jan 3, 2009 at 4:43 AM, Russell Keith-Magee
> wrote:
>> If there is some technical reason why the django.contrib namespace is
>> required, then raise that issue on the developers list and we can see
>&
Hi all,
SQL Aggregations (ticket #3566) are almost ready for trunk!
This is a call for final testing. My aim is to have this committed for
the original v1.1 Jan 15 deadline, possibly sooner (depending on the
feedback received). If you want to help out with testing, the code is
available from my
Hi all,
I have a design issue on ticket #7210 that requires some feedback from
the community.
For those that haven't been following along, Ticket #7210 is about
adding the ability to reference fields during a query. Two quick
examples of common use cases:
Find all the hotel rooms that have the
On Mon, Jan 5, 2009 at 8:22 PM, Ivan Sagalaev
wrote:
>
> Malcolm Tredinnick wrote:
>> Russ, Nicolas and, to some extent, myself, have been working fairly
>> solidly on the aggregates stuff which is now close to completion (I've
>> got one thing to commit before Russ does a final merge).
>
> BTW d
On Tue, Jan 6, 2009 at 12:51 AM, alex.gay...@gmail.com
wrote:
>
> Karen,
>
> Can you try changing line 230 of django.db.models.sql.query from:
>row = row[:aggregate_start] + tuple(
> to
>row = tuple(row[:aggregate_start]) + tuple(
>
> That should clear up m
On Tue, Jan 6, 2009 at 1:21 AM, Alex Gaynor wrote:
> The one's that are a result of Oracle not returning a Decimal can be solved
> be inserting "..." before and after the number, in placeess of explicitly
> saying Decimal(unless of course this is actually a typecasting issue in
> Django itself, i
On Tue, Jan 6, 2009 at 8:11 AM, Malcolm Tredinnick
wrote:
>
> On Mon, 2009-01-05 at 23:11 +0900, Russell Keith-Magee wrote:
>> Hi all,
>>
>> SQL Aggregations (ticket #3566) are almost ready for trunk!
>>
>> This is a call for final testing.
>
> By the
On Tue, Jan 6, 2009 at 11:16 AM, Alex Gaynor wrote:
> The datetime issue looks like it's just an issue of porting this logic:
> http://code.djangoproject.com/browser/django/trunk/django/db/backends/oracle/query.py#L72
>
> over to the coerce aggregates function. There's a bit of decimal logic
> a
On Tue, Jan 6, 2009 at 7:52 PM, zvoase wrote:
>
> Just a question - how, if at all, is aggregation going to be supported
> or worked around on custom field types?
Do you have any particular fields in mind? Any custom field deriving
from the basic Django numeric and date/time types shouldn't requ
On Wed, Jan 7, 2009 at 4:19 AM, Ian Kelly wrote:
>
> On Tue, Jan 6, 2009 at 12:14 AM, Ian Kelly wrote:
>> On Mon, Jan 5, 2009 at 9:21 AM, Alex Gaynor wrote:
>>> The SQL command not properly ended appears to be the result of an annotate
>>> call followed by a call to aggregate(). I don't have a
On Wed, Jan 7, 2009 at 7:45 AM, Russell Keith-Magee
wrote:
> On Wed, Jan 7, 2009 at 4:19 AM, Ian Kelly wrote:
>>
>> On Tue, Jan 6, 2009 at 12:14 AM, Ian Kelly wrote:
>>> On Mon, Jan 5, 2009 at 9:21 AM, Alex Gaynor wrote:
>>>> The SQL command not properly
On Thu, Jan 8, 2009 at 1:36 AM, Alex Gaynor wrote:
> I've spent some time looking at this trying to implement expansion of
> related fields as Russ and I discussed last night. I have a few questions
> about the design choice that was implemented, why didn't you choose to go
> with this evaluator
Hi all,
I'm was just about ready to commit ticket #3566, but then Justin Bronn
threw a spanner in my works :-)
Justin pointed out a number of test failures that stem from the change
in Decimal.__repr__() to use single quotes rather than double quotes
in Python 2.6. The problems present like this
On Tue, Jan 13, 2009 at 4:59 AM, Karen Tracey wrote:
> One of the item on the list for 1.1 is "Run Django test cases inside a
> transaction". The ticket for this is #8138:
Thanks for picking up on this one, Karen. I thought I would have time
to look at this, but life conspired against me.
> So
On Wed, Jan 14, 2009 at 1:00 AM, Karen Tracey wrote:
> On Tue, Jan 13, 2009 at 9:05 AM, Russell Keith-Magee
> wrote:
>>
>> > So, the latest patch on #8183 (8138alternate-nodoctestxaction.diff) does
>> > not
>> > enclose doctest runs in a rolled
On Wed, Jan 14, 2009 at 7:38 AM, Karen Tracey wrote:
> On Tue, Jan 13, 2009 at 12:06 PM, Jacob Kaplan-Moss
> wrote:
>>
>> On Tue, Jan 13, 2009 at 10:00 AM, Karen Tracey wrote:
>> > OK, so that sounds like one vote for leaving things as they are for
>> > doctests, that is with no rolled-back tra
Hi all,
I have now finished work on ticket #3566 - adding aggregations to Django's ORM.
I intend to commit the code to Django's trunk tomorrow evening, my
time (i.e., in about 30 hours time).
If you have any objections or problem reports, speak now or live with
the consequences :-)
Yours,
Russ
On Thu, Jan 15, 2009 at 5:40 AM, Eric Holscher wrote:
> I think that if there is a plan to ever include fixtures into doctests, then
> we should put transaction management into them. We should also decide on a
> syntax (__fixtures__ really isn't too bad). This is mostly a bikeshed, where
> if it'
On Thu, Jan 15, 2009 at 4:20 AM, Ian Kelly wrote:
> On Wed, Jan 14, 2009 at 10:54 AM, Karen Tracey wrote:
>> I'm also seeing failures when using Oracle as the backend, many tracebacks
>> that end with:
>>
>> File "d:\u\kmt\django\aggregation\django\db\backends\oracle\query.py", line
>> 69, in co
2001 - 2100 of 2850 matches
Mail list logo
