Hi all. Sorry about the noise before regarding DateField/TimeField..
it wasn't an issue specific to this backend. It's actually a django
problem - details and fix at http://code.djangoproject.com/ticket/7801
Thanks.
On Jul 16, 9:51 am, bob84123 <[EMAIL PROTECTED]> wrote:
> Thanks for that.
On Thu, 2008-07-17 at 02:39 -0700, Göran Åström wrote:
> In my view the 'not' can be interpreted differently.
> Look at the following requests:
>
> 1. Give me blogs with entries matching a criteria.
> 2. Give me blogs with entries not matching a criteria.
> 3. Give me blogs without entries
On Thu, Jul 17, 2008 at 10:01 AM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> On Thu, Jul 17, 2008 at 6:46 AM, zvoase <[EMAIL PROTECTED]> wrote:
>>
>> Dear Developers,
>> I've written a module which may be helpful to a lot of Django
>> developers, and would like to suggest it for trials and
On Jul 17, 2008, at 4:26 AM, Ross Lawley wrote:
> Hi all,
>
> The recent changes in newforms admin r7529 changed the validation
> for newforms admin models. However, it is a bit too strict and
> doesn't allow customizable admin forms to output non model fields.
>
> I've added a patch with
On Thu, Jul 17, 2008 at 6:46 AM, zvoase <[EMAIL PROTECTED]> wrote:
>
> Dear Developers,
> I've written a module which may be helpful to a lot of Django
> developers, and would like to suggest it for trials and testing, and
> possible inclusion with Django.
Well, for starters, it appears to be
> In summary, it is called 'QManager', and is a Manager subclass which
> helps developers create Managers from Q objects. QManager instances
> can be joined by & and |, and by using the negative operator you can
> create a QManager which is the complement of the original.
Whether included in
Yes, that's why the proposed patch for the documentation says that
both must be of the same type:
http://code.djangoproject.com/attachment/ticket/7785/note-about-primary-keys.diff
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed
A documentation change about using a different field type is not
enough in some cases (PostgreSQL 8.3), as noted in #6523 [1].
PostgreSQL 8.3 won't implicitly cast variables anymore, so if you pick
integer for your generic relation you'll have problems relating models
with varchar, and vice
Dear Developers,
I've written a module which may be helpful to a lot of Django
developers, and would like to suggest it for trials and testing, and
possible inclusion with Django. I'm currently just looking for
developers to help test and work with the module; it should be quite
helpful.
In
In my view the 'not' can be interpreted differently.
Look at the following requests:
1. Give me blogs with entries matching a criteria.
2. Give me blogs with entries not matching a criteria.
3. Give me blogs without entries matching a criteria.
All three are valid.
In django 0.96 number 1 and 2
Sorry gmail munged the ticket url: http://code.djangoproject.com/ticket/7790
On Jul 17, 11:26 am, "Ross Lawley" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> The recent changes in newforms admin r7529 changed the validation for
> newforms admin models. However, it is a bit too strict and doesn't
Hi all,
The recent changes in newforms admin r7529 changed the validation for
newforms admin models. However, it is a bit too strict and doesn't allow
customizable admin forms to output non model fields.
I've added a patch with tests to:
http://code.djangoproject.com/ticket/7790- which also
On 17 jul, 02:05, "Robert Coup" <[EMAIL PROTECTED]>
wrote:
> Its not that hard to handle...
>
> 1. Have long-lived sessions:
> - if there isn't a user associated: "anonymous"
> - if it has a user: "known"
>
> 2. When a user logs in (ie. types their username and password):
> - add the user
13 matches
Mail list logo
